All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Eino-Ville Talvala <talvala@stanford.edu>
Cc: Zach LeRoy <zleroy@rii.ricoh.com>,
	"Aguirre Rodriguez, Sergio" <saaguirre@ti.com>,
	linux-media <linux-media@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Problems configuring OMAP35x ISP driver
Date: Sun, 19 Jul 2009 09:07:50 -0600	[thread overview]
Message-ID: <4A6336C6.8030807@mlbassoc.com> (raw)
In-Reply-To: <4A5CBF3D.80002@stanford.edu>

Eino-Ville Talvala wrote:
> Zach,
> 
> We've gotten a Aptina MT9P031 driver working with the latest ISP
> patchset, both with YUV and RAW data.
> I don't know what the problem might be with YUYV data - we get useful
> YUYV data without any changes to the ISP defaults.
> However, to request RAW data, that simply uses the CCDC and bypasses all
> the processing in the ISP, request the pixelformat of
> V4L2_PIX_FMT_SGRBG10.  This will give you two bytes per pixel, at least
> in our case (although we have a 12-bit sensor cut down to 10 bits), so
> be prepared to throw out every other byte.
> 
> Hope this helps,
> 
> Eino-Ville (Eddy) Talvala
> Computer Graphics Lab
> Stanford University
> 

I've been working on this same issue, using a Micron MT9T001 sensor, without
much success.  Could you share your tree and/or patches (against what?)??
This would be most helpful.

Thanks

> On 7/14/2009 9:49 AM, Zach LeRoy wrote:
>> Hello Sergio,
>>
>> I spoke with you earlier about using the ISP and omap34xxcam drivers
>> with a micron mt9d111 SOC sensor.  I have since been able to take
>> pictures, but the sensor data is not making it through the ISP
>> data-path correctly.  I know the problem is in the ISP data-path
>> because I am configuring the sensor the exact same way as I have been
>> on my working PXA system.  I am expecting 4:2:2 packed YUV data, but
>> all of the U and V data is no more than 2 bits where it should be 8. 
>> I know the ISP has a lot of capabilities, but all I want to use it for
>> is grabbing 8-bit data from my sensor and putting it in a buffer
>> untouched using the CCDC interface (and of course clocking and
>> timing).  What are the key steps to take to get this type of
>> configuration?
>>
>> Other Questions:
>>
>> Is there any processing done on YUV data in the ISP driver by default
>> that I am missing?
>> Has any one else experienced similar problems while adding new sensor
>> support?
>>
>> Any help here would be greatly appreciated.
>>
>> Thank you,
>>
>> Zach LeRoy



-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

      parent reply	other threads:[~2009-07-19 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17937063.23811247589353235.JavaMail.root@mailx.crc.ricoh.com>
2009-07-14 16:49 ` Problems configuring OMAP35x ISP driver Zach LeRoy
2009-07-14 16:58   ` AW: " Jesko Schwarzer
2009-07-14 16:58     ` Jesko Schwarzer
2009-07-14 17:24   ` Eino-Ville Talvala
2009-07-14 20:51     ` John Sarman
2009-07-14 20:51       ` John Sarman
     [not found]       ` <4A5E11B9.9010504@stanford.edu>
2009-07-15 17:38         ` John Sarman
2009-07-19 15:07     ` Gary Thomas [this message]

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=4A6336C6.8030807@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=saaguirre@ti.com \
    --cc=talvala@stanford.edu \
    --cc=zleroy@rii.ricoh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.