public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Using MT9P031 digital sensor
Date: Tue, 08 Nov 2011 05:52:25 -0700	[thread overview]
Message-ID: <4EB92609.1060703@mlbassoc.com> (raw)
In-Reply-To: <CAAwP0s0joZbNLDzR-WkwFBgOpyZ+=hvbMROQs+LTTyNCpfccTw@mail.gmail.com>

On 2011-11-08 05:30, Javier Martinez Canillas wrote:
> On Tue, Nov 8, 2011 at 1:20 PM, Gary Thomas<gary@mlbassoc.com>  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
------------------------------------------------------------

  parent reply	other threads:[~2011-11-08 12:52 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 18:52 Using MT9P031 digital sensor Gary Thomas
2011-11-04 10:37 ` Laurent Pinchart
2011-11-08 12:20   ` Gary Thomas
2011-11-08 12:30     ` Javier Martinez Canillas
2011-11-08 12:33       ` Laurent Pinchart
2011-11-08 12:52       ` Gary Thomas [this message]
2011-11-08 13:06         ` Laurent Pinchart
2011-11-08 13:38           ` Gary Thomas
2011-11-08 13:40             ` Gary Thomas
2011-11-09  0:54             ` Laurent Pinchart
2011-11-09 11:01               ` Gary Thomas
2011-11-09 16:18                 ` Laurent Pinchart
2011-11-09 16:24                   ` Gary Thomas
2011-11-11 14:26                     ` Laurent Pinchart
2011-11-14 11:42                       ` Gary Thomas
2011-11-16  1:26                         ` Laurent Pinchart
2011-11-16 12:03                           ` Gary Thomas
2011-11-24 11:28                             ` Laurent Pinchart
2011-11-25 11:50                               ` Gary Thomas
2011-11-28 11:07                                 ` Laurent Pinchart
2011-11-28 12:42                                   ` Gary Thomas
2011-11-28 12:49                                     ` Laurent Pinchart
2011-11-28 12:53                                       ` Gary Thomas
2011-11-30 14:13                                       ` Gary Thomas
2011-11-30 14:30                                         ` Laurent Pinchart
2011-11-30 14:38                                           ` Hiremath, Vaibhav
2011-11-30 14:57                                           ` Gary Thomas
2011-11-30 17:00                                             ` Gary Thomas
2011-11-30 23:49                                               ` Laurent Pinchart
2011-11-30 23:42                                             ` Laurent Pinchart
  -- strict thread matches above, loose matches on Subject: below --
2012-03-23 19:01 Joshua Hintze
2012-03-26  5:13 ` Joshua Hintze
2012-03-26  8:25   ` Laurent Pinchart
2012-03-26 15:44     ` Joshua Hintze
2012-03-26 17:38       ` Laurent Pinchart
2012-03-26 17:43         ` Joshua Hintze
     [not found]   ` <4F708A66.8090303@mlbassoc.com>
2012-03-26 15:37     ` Joshua Hintze
2012-03-26 16:32       ` Gary Thomas
2012-03-26 16:55         ` Joshua Hintze
2012-03-27 14:44         ` jean-philippe francois
2012-03-29 11:33           ` Laurent Pinchart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EB92609.1060703@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=martinez.javier@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox