From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Tim Harvey <tharvey@gateworks.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH REPOST] TDA1997x: replace video detection routine
Date: Fri, 23 Jul 2021 13:57:06 +0200 [thread overview]
Message-ID: <m3eebpckfh.fsf@t19.piap.pl> (raw)
In-Reply-To: <798b2128-24a6-1a62-f98c-f228134e8d5c@xs4all.nl> (Hans Verkuil's message of "Fri, 23 Jul 2021 10:49:01 +0200")
Hi Hans,
Hans Verkuil <hverkuil@xs4all.nl> writes:
> The tda1997x doesn't have any method of obtaining the sync polarities?
>
> HSync and VSync are, as you say, using in-band signaling, but the 'polarity'
> still matters when it comes to detecting timings. All HDMI receivers I have
> ever seen have a register that reports the polarities. I find it *very* hard
> to imagine that this device doesn't support that.
I didn't know that HDMI serializers send the logical levels of those
lines, I thought some frame/field/line start/end codes are sent instead.
I will have to have a closer look at this chip, then.
> Do you have a datasheet for this device?
No, there is only the current driver and also the old one (in Gateworks'
Freescale/NXP kernel). Tim may have something perhaps under NDA, maaybe.
I will see if I can find these bits in the registers.
Thanks.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
prev parent reply other threads:[~2021-07-23 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 9:30 [PATCH REPOST] TDA1997x: replace video detection routine Krzysztof Hałasa
2021-07-21 7:12 ` Hans Verkuil
2021-07-21 7:56 ` Krzysztof Hałasa
2021-07-21 10:04 ` Hans Verkuil
2021-07-22 6:27 ` Krzysztof Hałasa
2021-07-22 6:43 ` Krzysztof Hałasa
2021-07-23 8:24 ` Hans Verkuil
2021-07-23 8:49 ` Hans Verkuil
2021-07-23 11:57 ` Krzysztof Hałasa [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=m3eebpckfh.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--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 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.