Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [RFC PATCH 2/5] drm/i915/display: add pme_capable() to the parent interface
Date: Tue, 18 Aug 2026 06:54:10 +0000	[thread overview]
Message-ID: <38839928b5b5147989959741068c001ce180eb0b.camel@intel.com> (raw)
In-Reply-To: <bb80200efea31ed150318deaa8622d8efddb2666@intel.com>

On Mon, 2026-08-17 at 13:19 +0300, Jani Nikula wrote:
> On Mon, 17 Aug 2026, Vinod Govindapillai
> <vinod.govindapillai@intel.com> wrote:
> > Add a provision to query the optional pme_capability to the parent
> > interface so that it could be called independently from xe or i915
> > based on the implementation.
> 
> But do we need this? Display has all the information to call
> pci_dev_run_wake() directly, without going through the parent
> interface.
> 
> The only difference is this is not being set up for i915.

Ok. Yeah pci_dev_run_wake() should handle this properly. But because
the platform support for the pme is added from NVL, I thought of this
approach. 

So you are suggesting something like this?

if (pci_dev_run_wake()), avoid start HPD polling directly in the 
intel_display_driver::intel_display_driver_pm_runtime_suspend()?

Or use a wrapper to check the pme_capability.

BR
Vinod 

> BR,
> Jani.
> 
> > 
> > Assisted-by: GitHub_Copilot:claude-opus-5
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_display_rpm.c | 7 +++++++
> >  drivers/gpu/drm/i915/display/intel_display_rpm.h | 1 +
> >  include/drm/intel/display_parent_interface.h     | 1 +
> >  3 files changed, 9 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_rpm.c
> > b/drivers/gpu/drm/i915/display/intel_display_rpm.c
> > index 0a331f89b4db..73d85384474e 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_rpm.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display_rpm.c
> > @@ -46,6 +46,13 @@ bool intel_display_rpm_suspended(struct
> > intel_display *display)
> >  	return display->parent->rpm->suspended(display->drm);
> >  }
> >  
> > +bool intel_display_rpm_pme_capable(struct intel_display *display)
> > +{
> > +	const struct intel_display_rpm_interface *rpm = display-
> > >parent->rpm;
> > +
> > +	return rpm->pme_capable && rpm->pme_capable(display->drm);
> > +}
> > +
> >  void assert_display_rpm_held(struct intel_display *display)
> >  {
> >  	display->parent->rpm->assert_held(display->drm);
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_rpm.h
> > b/drivers/gpu/drm/i915/display/intel_display_rpm.h
> > index 6ef48515f84b..2d4071fb9282 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_rpm.h
> > +++ b/drivers/gpu/drm/i915/display/intel_display_rpm.h
> > @@ -21,6 +21,7 @@ void intel_display_rpm_put(struct intel_display
> > *display, struct ref_tracker *wa
> >  
> >  /* Only for special cases. */
> >  bool intel_display_rpm_suspended(struct intel_display *display);
> > +bool intel_display_rpm_pme_capable(struct intel_display *display);
> >  
> >  void assert_display_rpm_held(struct intel_display *display);
> >  void intel_display_rpm_assert_block(struct intel_display
> > *display);
> > diff --git a/include/drm/intel/display_parent_interface.h
> > b/include/drm/intel/display_parent_interface.h
> > index d7d06dcaa699..563de403b102 100644
> > --- a/include/drm/intel/display_parent_interface.h
> > +++ b/include/drm/intel/display_parent_interface.h
> > @@ -196,6 +196,7 @@ struct intel_display_rpm_interface {
> >  	void (*put_unchecked)(const struct drm_device *drm);
> >  
> >  	bool (*suspended)(const struct drm_device *drm);
> > +	bool (*pme_capable)(const struct drm_device *drm); /*
> > Optional */
> >  	void (*assert_held)(const struct drm_device *drm);
> >  	void (*assert_block)(const struct drm_device *drm);
> >  	void (*assert_unblock)(const struct drm_device *drm);
> 


  reply	other threads:[~2026-08-18  6:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16 22:39 [RFC PATCH 0/5] pm_pme support on display hotplug Vinod Govindapillai
2026-08-16 22:40 ` [RFC PATCH 1/5] drm/xe/pm: add xe_pm_pme_supported() helper Vinod Govindapillai
2026-08-17 10:17   ` Jani Nikula
2026-08-16 22:40 ` [RFC PATCH 2/5] drm/i915/display: add pme_capable() to the parent interface Vinod Govindapillai
2026-08-17 10:19   ` Jani Nikula
2026-08-18  6:54     ` Govindapillai, Vinod [this message]
2026-08-18  6:57       ` Jani Nikula
2026-08-16 22:40 ` [RFC PATCH 3/5] drm/i915/xe: plug the pme_capability query for xe Vinod Govindapillai
2026-08-16 22:40 ` [RFC PATCH 4/5] drm/i915/display: add intel_hpd_polling_enabled() Vinod Govindapillai
2026-08-16 22:40 ` [RFC PATCH 5/5] drm/i915/display: skip HPD polling if PME is supported Vinod Govindapillai
2026-08-16 22:52   ` sashiko-bot
2026-08-17 10:15   ` Jani Nikula
2026-08-16 22:48 ` ✓ CI.KUnit: success for pm_pme support on display hotplug Patchwork
2026-08-16 23:26 ` ✗ Xe.CI.BAT: 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=38839928b5b5147989959741068c001ce180eb0b.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 \
    /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