From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from hermes.mlbassoc.com ([64.234.241.98]:43717 "EHLO mail.chez-thomas.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751733Ab1KHMw0 (ORCPT ); Tue, 8 Nov 2011 07:52:26 -0500 Message-ID: <4EB92609.1060703@mlbassoc.com> Date: Tue, 08 Nov 2011 05:52:25 -0700 From: Gary Thomas MIME-Version: 1.0 To: Javier Martinez Canillas CC: Laurent Pinchart , Linux Media Mailing List Subject: Re: Using MT9P031 digital sensor References: <4EB04001.9050803@mlbassoc.com> <201111041137.08254.laurent.pinchart@ideasonboard.com> <4EB91E7C.4050302@mlbassoc.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: On 2011-11-08 05:30, Javier Martinez Canillas wrote: > On Tue, Nov 8, 2011 at 1:20 PM, Gary Thomas wrote: >> On 2011-11-04 04:37, Laurent Pinchart wrote: >>> >>> Hi Gary, >>> >>> On Tuesday 01 November 2011 19:52:49 Gary Thomas wrote: >>>> >>>> I'm trying to use the MT9P031 digital sensor with the Media Controller >>>> Framework. media-ctl tells me that the sensor is set to capture using >>>> SGRBG12 2592x1944 >>>> >>>> Questions: >>>> * What pixel format in ffmpeg does this correspond to? >>> >>> I don't know if ffmpeg supports Bayer formats. The corresponding fourcc in >>> V4L2 is BA12. >> >> ffmpeg doesn't seem to support these formats >> >>> >>> If your sensor is hooked up to the OMAP3 ISP, you can then configure the >>> pipeline to include the preview engine and the resizer, and capture YUV >>> data >>> at the resizer output. >> >> I am using the OMAP3 ISP, but it's a bit unclear to me how to set up the >> pipeline > > Hi Gary, > > I'm also using another sensor mtv9034 with OMAP3 ISP, so maybe I can help you. > >> using media-ctl (I looked for documentation on this tool, but came up dry - >> is there any?) >> >> Do you have an example of how to configure this using the OMAP3 ISP? >> > > This is how I configure the pipeline to connect the CCDC with the > Previewer and Resizer: > > ./media-ctl -l '"mt9v032 3-005c":0->"OMAP3 ISP CCDC":0[1]' > ./media-ctl -l '"OMAP3 ISP CCDC":2->"OMAP3 ISP preview":0[1]' > ./media-ctl -l '"OMAP3 ISP preview":1->"OMAP3 ISP resizer":0[1]' > ./media-ctl -l '"OMAP3 ISP resizer":1->"OMAP3 ISP resizer output":0[1]' > ./media-ctl -f '"mt9v032 3-005c":0[SGRBG10 752x480]' > ./media-ctl -f '"OMAP3 ISP CCDC":0 [SGRBG10 752x480]' > ./media-ctl -f '"OMAP3 ISP CCDC":1 [SGRBG10 752x480]' > ./media-ctl -f '"OMAP3 ISP preview":0 [SGRBG10 752x479]' > ./media-ctl -f '"OMAP3 ISP resizer":0 [YUYV 734x471]' > ./media-ctl -f '"OMAP3 ISP resizer":1 [YUYV 640x480]' > > Hope it helps, > Thanks, I'll give this a try. I assume that your sensor is probably larger than 752x480 (the mt9p031 is 2592x1944 raw) and that setting the smaller frame size enables some scaling and/or cropping in the driver? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------