Hi Laurent, On Fri, Dec 16, 2011 at 5:40 PM, Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> wrote: > Hi James, > > On Friday 16 December 2011 01:53:59 James wrote: >> On Thu, Dec 15, 2011 at 6:10 PM, Michael Jones wrote: >> > On 12/15/2011 10:49 AM, James wrote: >> >> On Thu, Dec 15, 2011 at 3:58 PM, Michael Jones wrote: >> >>> On 12/15/2011 08:14 AM, James wrote: >> >>>> Hi all, >> >>>> >> >>>> I'm using an OMAP3530 board and a monochrome 12-bit grey sensor. >> >>>> >> >>>> Can anyone enlighten me why is the 12-bit grey formats at the CCDC >> >>>> input (Y12) is truncated to Y10 at the CCDC output? >> >>> >> >>> There are 2 CCDC outputs: CCDC_PAD_SOURCE_OF and CCDC_PAD_SOURCE_VP. >> >>> Only the VP (video port) truncates data to 10 bits, and it does that >> >>> because the >> >>> subdevs it feeds can only handle 10 bits max. >> >> >> >> Thank you for the clarification. >> >> >> >>>> I need to read the entire RAW 12-bit grey value from the CCDC to >> >>>> memory and the data does not pass through other OMAP3ISP sub-devices. >> >>>> >> >>>> I intend to use Laurent's yavta to capture the data to file to verify >> >>>> its operation for the moment. >> >>>> >> >>>> Can this 12-bit (Y12) raw capture be done? >> >>> >> >>> Yes. If you are writing the 12-bit gray value directly into memory, you >> >>> will >> >>> use SOURCE_OF and can write the full 12-bits into memory. You need to >> >>> set >> >>> up your media pipeline to do sensor->CCDC->OMAP3 ISP CCDC output. >> >> >> >> Is there further modification needed to apply to the OMAP3ISP to achieve >> >> this? >> >> >> >> Do you have an application to test the pipeline for this setting to >> >> simple display? >> > >> > Let's establish where you're coming from. Are you familiar with the >> > media controller? Laurent has a program 'media-ctl' to set up the >> > pipeline (see http://git.ideasonboard.org/?p=media-ctl.git). You will >> > find many examples of its usage in the archives of this mailing list. It >> > will look something like: >> > media-ctl -r >> > media-ctl -l '"OMAP3 ISP CCDC":1 -> "OMAP3 ISP CCDC output":0 [1]' >> > media-ctl -l '"your-sensor-name":0 -> "OMAP3 ISP CCDC":0 [1]' >> > >> > you will also need to set the formats through the pipeline with >> > 'media-ctl --set-format'. >> > >> > After you use media-ctl to set up the pipeline, you can use yavta to >> > capture the data from the CCDC output (for me, this is /dev/video2). >> >> Yes, I've been using Laurent's media-ctl & yavta to test out MT9V032 >> on the Overo board. >> He has been helping and guiding me with it as there isn't any success >> with using MT9V032 on the Overo board then. (^^) >> >> What I've been looking for since then is any other application such as >> GUI MPlayer or gst-launch that can open the device and playback the >> data to either LCD or DVI display on the board. (i.e. direct >> 'streaming') >> >> Do you know of any? I wish to avoid any further components (e.g. >> ffmpeg) that modify/convert the raw data as much as possible. >> >> sensor->CCDC->application->display > > If you're going to display the data, the 12-bit resolution is overkill. You > can thus limit it to 10-bits in the CCDC, and you should feed it to the > preview engine (and possibly resizer) to get YUV which could easily be played > on screen. Yup. The main purpose of grabbing at 12-bit is for soft post-processing before being fed to the display at its optimal resolution. Thus, I've to bypass all the HW ISP blocks available in the OMAP3530. For now, I just need a method to validate the proof-of-concept of the pipeline with a 'grab-n-dump' streaming playback without any post-processing onto the display (LCD/DVI). > However, the preview engine doesn't support Y10 input yet, so this will need > to be implemented. Noted. > You can work around the problem by hacking the sensor > driver to report SGRBG10. You will get a resulting YUV image that will look > more or less correct, but with color artifacts. That's at least a temporary > solution to make sure the pipeline + display are working. The hack is to keep the constant (V4L2_MBUS_FMT_SGRBG10_1X10) instead of changing to V4L2_MBUS_FMT_Y12_1x12? Many thanks in adv. -- Regards, James -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
