From: Steve Longerbeam <slongerbeam@gmail.com>
To: Tim Harvey <tharvey@gateworks.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: IMX CSI capture issues with tda1997x HDMI receiver
Date: Sun, 27 Jan 2019 14:36:05 -0800 [thread overview]
Message-ID: <4b7b9a4f-f178-b5bb-1813-fba55d1f6749@gmail.com> (raw)
In-Reply-To: <02e8680c-9fd5-ff54-f292-f6936c76583e@gmail.com>
Hi Tim,
On 1/25/19 3:57 PM, Steve Longerbeam wrote:
<snip>
>> Now lets go back to a 480p60 source but this time include the vdic
>> (which isn't necessary but should still work right?)
>
> No. First, the CSI will only capture in bt.656 mode if it sees
> interlaced fields (bt.656 interlaced sync codes). Well, let me
> rephrase, the CSI does support progressive BT.656 but I have never
> tested that myself.
One more comment here. It would be great if you could test a progressive
bt.656 sensor (example: imx6q-gw54xx tda19971 480p60Hz YUV via BT656
IPU1_CSI0) since as I said I've never been able to test this myself.
Since it is progressive there's no need for the VDIC, so try these
pipelines:
mode0: sensor -> mux -> csi -> /dev/videoN
mode1: sensor -> mux -> csi -> ic_prp -> ic_prpenc -> /dev/videoN
Steve
next prev parent reply other threads:[~2019-01-27 22:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 23:21 IMX CSI capture issues with tda1997x HDMI receiver Tim Harvey
2019-01-25 23:57 ` Steve Longerbeam
2019-01-27 22:36 ` Steve Longerbeam [this message]
2019-01-28 19:14 ` Tim Harvey
2019-01-28 23:05 ` Steve Longerbeam
2019-01-28 19:03 ` Tim Harvey
2019-01-28 23:04 ` Steve Longerbeam
2019-01-31 1:18 ` Tim Harvey
2019-02-02 19:10 ` Steve Longerbeam
2019-02-03 19:37 ` Steve Longerbeam
2019-02-05 19:16 ` Tim Harvey
2019-02-05 23:52 ` Steve Longerbeam
2019-02-06 16:31 ` Tim Harvey
2019-02-08 1:15 ` Tim Harvey
2019-02-08 1:53 ` Steve Longerbeam
2019-02-08 21:23 ` Tim Harvey
2019-02-08 23:22 ` Steve Longerbeam
2019-02-11 17:13 ` Tim Harvey
2019-02-08 1:48 ` Steve Longerbeam
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=4b7b9a4f-f178-b5bb-1813-fba55d1f6749@gmail.com \
--to=slongerbeam@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=tharvey@gateworks.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;
as well as URLs for NNTP newsgroup(s).