From: Steve Longerbeam <slongerbeam@gmail.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: IMX CSI capture issues with tda1997x HDMI receiver
Date: Mon, 28 Jan 2019 15:05:02 -0800 [thread overview]
Message-ID: <61d2bd9f-29d0-89b9-8a54-c823738a5b5c@gmail.com> (raw)
In-Reply-To: <CAJ+vNU3LgMi1cLNeatR-Z71=4qMNsgxbmnG_Y5XYE9qD1PXDEA@mail.gmail.com>
On 1/28/19 11:14 AM, Tim Harvey wrote:
> On Sun, Jan 27, 2019 at 2:36 PM Steve Longerbeam <slongerbeam@gmail.com> wrote:
>> 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,
>
> These both work fine in all cases for 480p60Hz YUV via BT656.
Great! thanks for confirming.
Steve
>
> When I use 480p60Hz 'RGB' via BT656 mode0 works fine as the CSI does
> the colorspace conversion needed for coda but for mode1 I end up with
> the itu601 colorimetery issue from before that I'm still trying to
> find a solution for.
>
> Tim
next prev parent reply other threads:[~2019-01-28 23:05 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
2019-01-28 19:14 ` Tim Harvey
2019-01-28 23:05 ` Steve Longerbeam [this message]
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=61d2bd9f-29d0-89b9-8a54-c823738a5b5c@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).