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: Thu, 22 Jul 2021 08:27:27 +0200 [thread overview]
Message-ID: <m3mtqedfsg.fsf@t19.piap.pl> (raw)
In-Reply-To: <68bd6e41-4c32-240f-aa83-fd2b96929d45@xs4all.nl> (Hans Verkuil's message of "Wed, 21 Jul 2021 09:12:08 +0200")
Hans,
I have a problem with matching H/V sync polarities. It appears the
standard modes use different polarity settings, and HDMI doesn't have
separate sync lines, it uses in-band signaling. I don't know what
polarity should I set for the v4l2_find_dv_timings_cap() ->
v4l2_match_dv_timings() to succeed.
1. I can try all 4 combinations (+/+, +/-, -/+, -/-) and see if there is
a match. Seems weird to me.
2. I can add a flag to v4l2_find_dv_timings_cap() ->
v4l2_match_dv_timings() which asks for the polarities to be ignored.
3. I could add
#define V4L2_DV_VSYNC_POS_POL 0x00000001
#define V4L2_DV_HSYNC_POS_POL 0x00000002
+#define V4L2_DV_VSYNC_ANY_POL 0x00000004
+#define V4L2_DV_HSYNC_ANY_POL 0x00000008
and v4l2_match_dv_timings() would skip comparing them. A bit hacky.
4. I could also add
#define V4L2_DV_VSYNC_POS_POL 0x00000001
#define V4L2_DV_HSYNC_POS_POL 0x00000002
+#define V4L2_DV_VSYNC_NEG_POL 0x00000004
+#define V4L2_DV_HSYNC_NEG_POL 0x00000008
and, likewise, v4l2_match_dv_timings() would know what to do. This is
IMHO cleaner but requires much more changes in other code (like
drivers).
Any other idea?
Perhaps I should do "2"?
Thanks,
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next prev parent reply other threads:[~2021-07-22 6:27 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 [this message]
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
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=m3mtqedfsg.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.