From: Jerome Tollet <jerome.tollet@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, ankit.k.nautiyal@intel.com,
ville.syrjala@linux.intel.com,
Jerome Tollet <jerome.tollet@gmail.com>
Subject: Re: [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status
Date: Fri, 27 Feb 2026 14:16:38 +0100 [thread overview]
Message-ID: <20260227131638.33167-1-jerome.tollet@gmail.com> (raw)
In-Reply-To: <73e0de50-b7e3-4315-ab81-0a3ecebc2363@intel.com>
Hi Ankit, Ville,
Gentle ping on this patch series. As confirmed in my previous testing
(Feb 21), the SCDC polling patch works perfectly on kernel 6.19.2 with
my Alder Lake-N (N100) + Cisco Desk Pro (CS-DESKPRO-2) setup.
The isolated testing showed that the SCDC polling approach alone
resolves the 4K@60Hz HDMI issue, which aligns with both the HDMI 2.0
spec requirements and Windows driver behavior.
Is there anything else needed from my side to help move this forward?
Thanks,
Jerome
next prev parent reply other threads:[~2026-02-27 13:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 13:38 [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2026-01-28 10:12 [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status 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
[not found] <[email protected]>
2026-02-21 7:37 ` Jerome Tollet
[not found] <20260113143107.1446909-1-ankit.k.nautiyal@intel.com>
2026-03-26 5:41 ` Jerome Tollet
2026-04-01 11:23 ` Ville Syrjälä
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
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=20260227131638.33167-1-jerome.tollet@gmail.com \
--to=jerome.tollet@gmail.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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