public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Lane Brooks <lane@brooks.nu>
To: linux-media@vger.kernel.org
Subject: OMAP3 Bridge Problems
Date: Tue, 03 Aug 2010 09:26:48 -0600	[thread overview]
Message-ID: <4C583538.8060504@gmail.com> (raw)

Laurent and team,

I am using the OMAP3 ISP code from the devel branch on gitorious that I 
back ported to a 2.6.31 kernel. Raw bayer streaming to the CCDC output 
works fine. I am using parallel input with the bridge disabled in that mode.

I am having a problem when I switch the sensor to output YUV422 data. 
The YUV422 stream is a 8x2. If I only switch the sensor to YUV422 mode, 
then I can get the YUV422 data at the CCDC output, but the CCDC pads an 
extra zero byte in there and I only get half the image. So that works as 
expected. I was then hoping all I would have to do is enable the bridge 
to get the YUV422_8x2 data packed into the YUV422_16x1 automatically, 
but instead I get select timeouts.

My question:

- Are there other things I need to when I enable the parallel bridge? 
For example, do I need to change a clock rate somewhere? From the TRM, 
it seems like it should just work without any changes, but maybe I am 
missing something.

Thanks,
Lane

             reply	other threads:[~2010-08-03 15:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 15:26 Lane Brooks [this message]
2010-08-04 20:57 ` OMAP3 Bridge Problems Laurent Pinchart
2010-08-05 16:06   ` Lane Brooks
2010-08-05 18:53     ` Lane Brooks
2010-08-08 22:29       ` Laurent Pinchart
2010-08-08 22:56         ` Lane Brooks
2010-08-09  9:25           ` Laurent Pinchart
2010-08-09 13:38             ` Lane Brooks
2010-09-03 13:39               ` Laurent Pinchart
2010-08-05 19:01     ` Lane Brooks
2010-08-08 22:13     ` Laurent Pinchart
2010-08-08 22:34       ` Lane Brooks
2010-08-08 22:37         ` 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=4C583538.8060504@gmail.com \
    --to=lane@brooks.nu \
    --cc=linux-media@vger.kernel.org \
    /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