From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: linux-media@vger.kernel.org
Subject: Re: OMAP3 ISP & BT656
Date: Mon, 26 May 2014 22:10:58 +0200 [thread overview]
Message-ID: <1508483.ine07GQHKa@avalon> (raw)
In-Reply-To: <4F15ED39.4070604@mlbassoc.com>
Hi Gary,
On Tuesday 17 January 2012 14:50:49 you wrote:
> I have a number of boards with OMAP 3530/3730 that use the
> TVP5150AM1 video decoder. On most of these boards, I can
> capture reasonable quality video. However, I have some (more
> than a few which is reason for concern) where the video is
> either really bad or even the ISP doesn't seem to recognize
> the BT656 data stream. On the ones that have "bad" video,
> the data is all blown out and barely recognizable.
>
> All the boards are running the same kernel (3.0+ with the
> YUV patches that Lennart and others proposed late last year).
> I've verified that the component registers (ISPCCDC and TVP5150)
> match. I can't see what could be the cause of such radically
> variable behaviour.
>
> The one thing I've found is on the boards that don't work
> at all, the CCDC_SYN_MODE[FLDSTAT] bit is not toggling, which
> in turn causes no data to be pushed through the V4L2 pipeline.
>
> Any ideas what can cause this? More importantly, what I can
> try to fix it? The really scary thing is that all the boards
> in my lab work great, but in the factory (some 6000 miles away),
> more than not don't work :-(
>
> Would it be possible to configure the CCDC to capture the
> raw BT656 data? These boards are very small and it's impossible
> to get onto the video data lines going into the processor (they
> are all hidden within the circuit board).
>
> Any help/ideas gladly accepted.
I realize this is a *really* late reply :-)
Just for your information, I've posted patches to the linux-media mailing list
that add BT.656 support to the OMAP3 ISP driver. I've CC'ed you, in case you
would find them useful and/or want to test them.
I'm also wondering whether you have been to fix the BT.656 issue you've
described here.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-05-26 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 21:50 OMAP3 ISP & BT656 Gary Thomas
2012-01-17 22:05 ` Gary Thomas
2014-05-26 20:10 ` Laurent Pinchart [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=1508483.ine07GQHKa@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=gary@mlbassoc.com \
--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 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.