From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Jérôme Tollet" <jerome.tollet@gmail.com>,
intel-gfx@lists.freedesktop.org, ville.syrjala@linux.intel.com
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status
Date: Tue, 17 Feb 2026 13:44:08 +0530 [thread overview]
Message-ID: <251146fb-69da-4c21-90bf-ed13e2e40724@intel.com> (raw)
In-Reply-To: <CADN_a6NjO=x=bn=yTMJcgbb41_HUAHMS3G5U3jD20TyLvmGHRw@mail.gmail.com>
On 2/14/2026 9:47 PM, Jérôme Tollet wrote:
> Hi Ville, Ankit,
>
> Update on testing (Feb 14):
> After isolated testing of each patch on kernel 6.18.7, I can now
> definitively confirm:
>
> - SCDC polling patch ALONE: Works perfectly ✓
> - delay patch (150ms) ALONE: Screen remains black ✗
> - Both patches together: Works (but delay is unnecessary)
>
> This definitively answers the question: approach #1 (Generic SCDC
> polling after port enable) is the correct solution. The v2 delay patch
> is NOT needed and should be disregarded.
>
> The SCDC polling aligns with HDMI 2.0 spec requirements and Windows
> behavior, making it the proper generic solution.
Thanks Jerome for testing.
Lets have all discussion in the original thread on the patch [1].
It seems your recent mails are on a separate thread.
Regards,
Ankit
[1]
https://lore.kernel.org/intel-xe/73e0de50-b7e3-4315-ab81-0a3ecebc2363@intel.com/
> Sorry for any confusion from my earlier messages.
>
> Thanks,
> Jerome
>
> Le sam. 7 févr. 2026 à 04:14, Jérôme Tollet <jerome.tollet@gmail.com> a écrit :
>> Hi Ville, Ankit,
>>
>> Gentle ping on this thread - it's been about 10 days since my last
>> message in the thread (Jan 28).
>>
>> To recap, we have three potential approaches for this fix:
>> 1. Generic SCDC polling after port enable (current patch) - aligns
>> with Windows behavior
>> 2. Panel-specific quirk for affected displays (Cisco Desk Pro in my case)
>> 3. Fixed delay after SCDC config (my v2 patch from Jan 14)
>>
>> Testing showed the delay works at any placement in the modeset
>> sequence, suggesting this is a timing issue rather than
>> operation-specific.
>> I'm happy to implement whichever approach you prefer. Please let me
>> know which direction you'd like me to take this.
>>
>> Thanks,
>> Jerome
>>
>>
>> Le mer. 28 janv. 2026 à 15:42, Jérôme Tollet <jerome.tollet@gmail.com> a écrit :
>>> Hi Ville,
>>> Following Ankit's response on January 21st where he suggested
>>> considering a panel-specific quirk instead of a generic solution, I
>>> wanted to get your input on the preferred approach.
>>> As a reminder, testing showed the delay works at any placement in the
>>> modeset sequence (all 4 test positions succeeded), suggesting this is
>>> a timing issue rather than being tied to a specific operation.
>>>
>>> Three approaches are available:
>>> 1. Generic SCDC polling after port enable - aligns with Windows
>>> behavior which also performs ~200ms SCDC poll post-enable
>>> 2. Panel-specific quirk for affected displays (Cisco Desk Pro in my case)
>>> 3. Fixed delay after SCDC config (my v2 patch from Jan 14)
>>>
>>> I'm happy with any approach that gets merged.
>>>
>>> Thanks
>>> Jerome
next prev parent reply other threads:[~2026-02-17 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADN_a6Ne4Vr6knCXdKtCnB8=et6OK7PEZ8F5bpyGamwyv1K9GA@mail.gmail.com>
2026-02-07 3:14 ` [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status Jérôme Tollet
2026-02-14 16:17 ` Jérôme Tollet
2026-02-17 8:14 ` Nautiyal, Ankit K [this message]
2026-01-13 13:38 Ankit Nautiyal
2026-01-13 21:39 ` Ville Syrjälä
2026-01-21 12:56 ` Nautiyal, Ankit K
2026-02-19 15:45 ` 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=251146fb-69da-4c21-90bf-ed13e2e40724@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jerome.tollet@gmail.com \
--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