From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jerome Tollet <jerome.tollet@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
ankit.k.nautiyal@intel.com
Subject: Re: [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status
Date: Wed, 1 Apr 2026 14:23:47 +0300 [thread overview]
Message-ID: <ac0AQ_74Tukshr__@intel.com> (raw)
In-Reply-To: <20260326054112.51287-1-jtollet@cisco.com>
On Thu, Mar 26, 2026 at 06:41:12AM +0100, Jerome Tollet wrote:
> From: Jerome Tollet <jerome.tollet@gmail.com>
>
> Hi Ankit, Ville,
>
> Following up on this patch.
>
> As previously reported, the SCDC polling approach fixes the 4K@60Hz HDMI
> issue on my Alder Lake-N (N100) + Cisco Desk Pro setup, and I have not
> seen regressions in testing.
>
> Ville, do you see any remaining concern with this approach, or is there
> anything else you would like me to test to help move this forward?
My main concern is having the synchronous polling appear to fix
something now, and if we later make it asynchronous the original
problem may re-appear.
That said, after perusing the spec a bit, it looks to me that sinks
should be able sync up after at most two video fields. I suppose
having effectively two extra vblank waits in a full modeset sequence
isn't the end of world. The extra complexity of asynchronous polling
might not even be worth the hassle.
But the commit message should still highlight that (AFAICS) synchronous
polling is not required by the spec, and thus the fact that this fixes
some monitors is sort of an accidental byproduct.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-04-01 11:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260113143107.1446909-1-ankit.k.nautiyal@intel.com>
2026-03-26 5:41 ` [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status Jerome Tollet
2026-04-01 11:23 ` Ville Syrjälä [this message]
2026-04-01 12:26 ` Jerome Tollet
2026-04-17 14:14 ` [PATCH v3] " Jerome Tollet
2026-04-20 20:15 ` ✗ LGCI.VerificationFailed: failure for drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status (rev3) Patchwork
2026-05-05 5:37 ` [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status Jerome Tollet
2026-05-06 10:11 ` ✗ LGCI.VerificationFailed: failure for drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status (rev4) Patchwork
2026-05-07 15:55 ` [PATCH] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status Jerome Tollet
[not found] <[email protected]>
2026-02-21 7:37 ` [RESEND] " Jerome Tollet
2026-01-28 10:12 Jérôme Tollet
2026-02-07 3:14 ` Jérôme Tollet
2026-02-14 16:17 ` Jérôme Tollet
2026-02-17 8:14 ` Nautiyal, Ankit K
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 13:38 Ankit Nautiyal
2026-01-13 14:48 ` ✓ i915.CI.BAT: success for " Patchwork
2026-01-13 20:56 ` ✗ i915.CI.Full: failure " Patchwork
2026-01-13 21:39 ` [RESEND] " Ville Syrjälä
2026-01-21 12:56 ` Nautiyal, Ankit K
2026-02-19 15:45 ` Jerome Tollet
2026-02-27 13:16 ` Jerome Tollet
2026-02-27 14:03 ` Nautiyal, Ankit K
2026-04-01 12:11 ` ✓ i915.CI.BAT: success for drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status (rev2) Patchwork
2026-04-02 4:23 ` ✓ i915.CI.Full: " Patchwork
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=ac0AQ_74Tukshr__@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jerome.tollet@gmail.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