From: Zach LeRoy <zleroy@rii.ricoh.com>
To: "Aguirre Rodriguez, Sergio" <saaguirre@ti.com>
Cc: linux-media <linux-media@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Problems configuring OMAP35x ISP driver
Date: Tue, 14 Jul 2009 09:49:18 -0700 (PDT) [thread overview]
Message-ID: <15157053.23861247590158808.JavaMail.root@mailx.crc.ricoh.com> (raw)
In-Reply-To: <17937063.23811247589353235.JavaMail.root@mailx.crc.ricoh.com>
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
next parent reply other threads:[~2009-07-14 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17937063.23811247589353235.JavaMail.root@mailx.crc.ricoh.com>
2009-07-14 16:49 ` Zach LeRoy [this message]
2009-07-14 16:58 ` AW: Problems configuring OMAP35x ISP driver Jesko Schwarzer
2009-07-14 17:24 ` Eino-Ville Talvala
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
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=15157053.23861247590158808.JavaMail.root@mailx.crc.ricoh.com \
--to=zleroy@rii.ricoh.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@ti.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