I'm trying to use adv7180 and dm365. By now vpfe_poll start, but no video incoming. I have to investigate configuration of vpfe in respect of adv7180 video format. adv7180 sees the video (status 1 register 0x4f). I'll send more info in future.
2010/3/26 Jean-Philippe François <[email protected]> > Karicheri, Muralidharan a écrit : > > Jean-Philippe, >> >> 4) Develop and integrate mt9p031 sensor driver and integrate it with >>>> >>> vpfe_capture. >>> Regarding point 4, how is the cmos capture part supposed to work with the >>> HD video standards ? >>> Currently, to set the cmos capture resolution we have to : >>> >>> set a video HD standards. >>> use TRY_FMT, S_FMT to set a windows that fits into the standard. >>> Currently, the highest resolution avilables are in the V4L2_STD_1080* >>> standard. >>> >>> mt9t* chips have resolution up to 2048x1536 >>> 2Mpixels sensor comes with resolution like 1600x1200 >>> not to mention the mt9p031 sensor. >>> >>> What is the right way to handle this ? >>> add a V4L2_STD_IMAGER_STD with a 4096x4096 or higher resolution ? >>> >>> >> I know this is an issue and was discussed in the v4l mailing list as >> part HD timing API RFC discussion. The conclusion then was to use S_FMT to >> set the frame size as done in mt9t031 driver. However currently >> mt9t031 doesn't allow setting frame rate. I think we need to discuss >> this in v4l list as part of this development activity. Another issue >> with the current implementation of mt9t031 is that how to make use >> of the Resizer at the VPFE to scale up or down the image output from the >> mt9t031. There is an effort to add device node to sub devices (Hans has >> indicated that to me last week). In that case, application may be able to >> use S_FMT at the sub device node and then call S_FMT at the video node >> (capture) and capture will be able to calculate proper scaling factor >> and apply the same at the Resizer. I suggest to discuss this as well >> in the v4l mailing list as part of this development activity. Another >> issue is how do we handle the i2c switch that is present in the sensor >> header? There are patches being reviewed in the i2c mailing list to >> handle these devices in the i2c driver. IMO, this piece is required as >> well. >> So do you want to work on this? >> > > I am sorry, I currently have no hardware with the corresponding cmos chips > at my disposal. But we are in the process of designing a new hardware, and > maybe > one of this sensor will be used. > > > >> -Murali >> >>> 5) one shot mode Preview and Resize drivers on DM355/DM365 using memory >>>> >>> to memory API (RFC recently submitted by Samsung) >>> >>>> 6) vpfe capture enhancements using Previewer and Resizer in continuous >>>> >>> mode. >>> >>>> 7) vpif display enhancements for HD video. >>>> 8) Adding AEW/AF/Histogram support in vpfe capture driver. >>>> >>>> Thanks. >>>> >>>> Murali Karicheri >>>> Software Design Engineer >>>> Texas Instruments Inc. >>>> Germantown, MD 20874 >>>> phone: 301-407-9583 >>>> email: [email protected] >>>> >>>> _______________________________________________ >>>> Davinci-linux-open-source mailing list >>>> [email protected] >>>> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source >>>> >>>> >> >> > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > -- www.opensurf.it
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
