From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "Deak, Imre" <imre.deak@intel.com>,
"Hogander, Jouni" <jouni.hogander@intel.com>
Subject: Re: [PATCH v5 06/10] drm/i915/hotplug: add helpers to track HPDs can generate PME
Date: Fri, 11 Sep 2026 15:36:13 +0000 [thread overview]
Message-ID: <5b664c22c7f83a3c899e4488159555954ea968ca.camel@intel.com> (raw)
In-Reply-To: <8005a243080166f9f328f7a58af857858626f027@intel.com>
On Fri, 2026-09-11 at 16:00 +0300, Jani Nikula wrote:
> On Fri, 11 Sep 2026, Vinod Govindapillai
> <vinod.govindapillai@intel.com> wrote:
> > As NVL+ devices can generate PME from HPDs, introduce a flag to
> > keep track of such a capability and helper functions to access
> > this flag. The plan is, this flag will be set to true from pm
> > runtime
> > suspend if PME is enabled and this flag will cleared on early
> > runtime
> > resume unconditionally. This is a place holder for the flag and
> > later
> > on this flag will be used for conditional IRQ resets and to decide
> > whether to do HPD polling.
>
> What's the rationale for duplicating the state in a flag? Why can't
> you
> use intel_display_rpm_pme_enabled() and have a single point of truth?
> This would dodge the extra error path clearing too.
>
> I don't understand.
>
> BR,
> Jani.
>
Ah..! Yes.. you are right. No rationale :( I kind of overlooked that
provision and was fixated on the steps I prepared before and fitting my
whole logic into that :(
Thanks. This is pretty clean. Will update.
Patches 6, 7,and 8 are indeed redundant and will remove those and use
the rpm_pme_enabled directly in avoiding the HPD resets and HPD polling
+ bool reset_hpd = !intel_display_rpm_pme_enabled(display);
and
+ if (intel_display_rpm_pme_enabled(display)) {
+ drm_dbg_kms(display->drm, "PME wake capable device,
skipping HPD polling.\n");
+ return;
+ }
Before send a new revision, hope there are no other comments. FYI
@Jouni.
BR
Vinod
> >
> > Bspec: 52979, 52980, 68857, 68867, 68970
> > Assisted-by: GitHub_Copilot:claude-opus-5
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
next prev parent reply other threads:[~2026-09-11 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 8:04 [PATCH v5 00/10] pm_pme support on display hotplug Vinod Govindapillai
2026-09-11 8:04 ` [PATCH v5 01/10] drm/xe/pm: initialize the device's system wakeup capabilities Vinod Govindapillai
2026-09-11 8:04 ` [PATCH v5 02/10] drm/xe/pm: introduce PM PME support Vinod Govindapillai
2026-09-11 8:04 ` [PATCH v5 03/10] drm/xe/pm: avoid reclaim when arming PME wakeup Vinod Govindapillai
2026-09-11 8:22 ` sashiko-bot
2026-09-11 8:04 ` [PATCH v5 04/10] drm/i915: add pme_enabled() to the parent interface Vinod Govindapillai
2026-09-11 8:04 ` [PATCH v5 05/10] drm/i915/xe: plug the pme_enabed implementation for xe Vinod Govindapillai
2026-09-11 8:04 ` [PATCH v5 06/10] drm/i915/hotplug: add helpers to track HPDs can generate PME Vinod Govindapillai
2026-09-11 13:00 ` Jani Nikula
2026-09-11 15:36 ` Govindapillai, Vinod [this message]
2026-09-11 8:04 ` [PATCH v5 07/10] drm/i915: plug the pm runtime handlers with PME HPD handling Vinod Govindapillai
2026-09-11 8:04 ` [PATCH v5 08/10] drm/xe/pm: clear PME HPD flag on runtime suspend error handler Vinod Govindapillai
2026-09-11 8:20 ` sashiko-bot
2026-09-11 8:04 ` [PATCH v5 09/10] drm/i915/irq: conditional HPD IRQ resets based on PME capability Vinod Govindapillai
2026-09-11 8:27 ` sashiko-bot
2026-09-11 8:04 ` [PATCH v5 10/10] drm/i915/hotplug: avoid HPD polling if the device is PME capable Vinod Govindapillai
2026-09-11 8:34 ` sashiko-bot
2026-09-11 9:19 ` ✓ i915.CI.BAT: success for pm_pme support on display hotplug (rev5) Patchwork
2026-09-12 5:04 ` ✗ i915.CI.Full: failure " 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=5b664c22c7f83a3c899e4488159555954ea968ca.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jouni.hogander@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