From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Jerome Tollet <jerome.tollet@gmail.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <ville.syrjala@linux.intel.com>,
<arun.r.murthy@intel.com>
Subject: Re: [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status
Date: Tue, 28 Jul 2026 20:15:47 +0530 [thread overview]
Message-ID: <a381bdf8-5c16-4b16-8770-4e565c8e65c7@intel.com> (raw)
In-Reply-To: <20260727131445.28048-1-jerome.tollet@gmail.com>
On 7/27/2026 6:44 PM, Jerome Tollet wrote:
> Hi Ankit,
>
> Following up on my last message from June 29, where I noted that commit
> b7d51d65e4f1 ("drm/i915/hdmi: Poll for 200 msec for
> TMDS_Scrambler_Status") was in drm-intel-next and asked about the next step.
>
> I also noticed that GitLab issue #6868 was closed on July 21 by Rob Clark
> with merge request !238.
>
> However, I checked the official Linux v7.2-rc5 sources and the helper
> intel_hdmi_poll_for_scrambling_enable() and its call are not present there.
>
> Could you please clarify whether the patch is queued for a later drm-intel
> pull, or whether a resend/rebase is needed for the v7.2 cycle?
>
> Please let me know if anything is still needed from my side.
Hi Jerome,
I checked with Jani regarding this. His comment was that commit
b7d51d65e4f1 was already part of the July 2 drm-intel-next pull request [1]
Beyond that, I'm not aware of the timeline for when that pull is
expected to land upstream.
I also don't see the commit in the v7.2-rc5 sources, so I can't comment
on its upstream status.
At least from my understanding, no further action is required from your
side at the moment.
[1]
https://lore.kernel.org/r/934cacdbf2a37856eb5cd6337d8774b449405bd8@intel.com
Thanks,
Ankit
>
> Thanks,
> Jerome
next prev parent reply other threads:[~2026-07-28 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 2:25 [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status Ankit Nautiyal
2026-05-20 2:47 ` ✓ CI.KUnit: success for drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status (rev3) Patchwork
2026-05-20 3:27 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-20 12:35 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-29 4:56 ` [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status Jerome Tollet
2026-06-09 9:31 ` Jerome Tollet
2026-06-11 9:03 ` Nautiyal, Ankit K
2026-06-29 6:17 ` Jerome Tollet
[not found] ` <20260727131445.28048-1-jerome.tollet@gmail.com>
2026-07-28 14:45 ` Nautiyal, Ankit K [this message]
[not found] <CADN_a6Ne4Vr6knCXdKtCnB8=et6OK7PEZ8F5bpyGamwyv1K9GA@mail.gmail.com>
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 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=a381bdf8-5c16-4b16-8770-4e565c8e65c7@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@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