Re: Why is the Y12 support 12-bit grey formats at the CCDC input (Y12) is truncated to Y10 at the CCDC output?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi James,

On Wednesday 21 December 2011 04:06:33 James wrote:
> On Wed, Dec 21, 2011 at 10:50 AM, James wrote:
> > On Thu, Dec 15, 2011 at 6:10 PM, Michael Jones wrote:
> >> Hi James,
> >> 
> >> 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).
> >> 
> >> 
> >> -Michael
> > 
> > I encountered some obstacles with the driver testing of my monochrome
> > sensor on top of Steve's 3.0-pm branch. An NXP SC16IS750 I2C-UART
> > bridge is used to 'transform' the sensor into a I2C device.
> > 
> > The PCLK, VSYNC, HSYNC (640x512, 30Hz, fixed output format) are free
> > running upon power-on the sensor unlike MT9V032 which uses the XCLKA
> > to 'power-on/off' it.
> > 
> > My steps,
> > 
> > 1) media-ctl -r -l '"mono640":0->"OMAP3 ISP CCDC":0:[1], "OMAP3 ISP
> > CCDC":1->"OMAP3 ISP CCDC output":0[1]'
> > 
> > Resetting all links to inactive
> > Setting up link 16:0 -> 5:0 [1]
> > Setting up link 5:1 -> 6:0 [1]
> > 
> > 2) media-ctl -f '"mono640":0[Y12 640x512]", "OMAP3 ISP CCDC":1[Y12
> > 640x512]'
> > 
> > Setting up format Y12 640x512 on pad OMAP3 ISP CCDC/0
> > Setting up format Y12 640x512 on pad OMAP3 ISP CCDC/1
> > 
> > 3) yavta -p -f Y12 -s 640x512 -n 4 --capture=61 --skip 1 -F `media-ctl
> > -e "OMAP3 ISP CCDC output"` --file=./DCIM/Y12
> > 
> > Unsupported video format 'Y12'
> > 
> > Did I missed something?

I've just pushed a patch to the yavta repository to support Y10 and Y12. 
Please update.

> > What parameters did you supplied to yavta to test the Y10/Y12
> > 
> > Many thanks in adv.
> > Sorry if duplicated emails received.
> 
> I changed the parameters for yavta from "-f Y12" to "-f Y16"
> 
> yavta -p -f Y16 -s 640x512 -n 2 --capture=10 --skip 5 -F `media-ctl -e
> "OMAP3 ISP CCDC output"` --file=./DCIM/Y16
> 
> and there are 2 chunks of message at the console now and it ended with
> "Unable to request buffers: Invalid argument (22).".
> 
> I've attached the logfile here. (mono640.log)
> 
> Hope you can assist me to grab the raw Y12 data to file.

-- 
Regards,

Laurent Pinchart
--
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


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux