Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: Re: [PATCH 4/6] drm/xe/display: Runtime pm wrappers for display parent interface
Date: Wed, 22 Oct 2025 12:29:35 +0300	[thread overview]
Message-ID: <05cda4146015ff0d939f4e2656cde4f30087d71c@intel.com> (raw)
In-Reply-To: <20251022085548.876150-5-jouni.hogander@intel.com>

On Wed, 22 Oct 2025, Jouni Högander <jouni.hogander@intel.com> wrote:
> Implement runtime pm wrappers for xe driver and add them into display
> parent interface.
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
>  drivers/gpu/drm/xe/display/xe_display.c | 76 +++++++++++++++++++++++++
>  1 file changed, 76 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
> index 0e38c96eb6def..8b2b0c5b398db 100644
> --- a/drivers/gpu/drm/xe/display/xe_display.c
> +++ b/drivers/gpu/drm/xe/display/xe_display.c
> @@ -36,6 +36,7 @@
>  #include "intel_opregion.h"
>  #include "skl_watermark.h"
>  #include "xe_module.h"
> +#include "xe_pm.h"
>  
>  /* Ensure drm and display members are placed properly. */
>  INTEL_DISPLAY_MEMBER_STATIC_ASSERT(struct xe_device, drm, display);
> @@ -515,7 +516,82 @@ static void display_device_remove(struct drm_device *dev, void *arg)
>  	intel_display_device_remove(display);
>  }
>  
> +static struct ref_tracker *xe_rpm_get(const struct drm_device *drm)
> +{
> +	return xe_pm_runtime_resume_and_get(to_xe_device(drm)) ? INTEL_WAKEREF_DEF : NULL;
> +}
> +
> +static struct ref_tracker *xe_rpm_get_raw(const struct drm_device *drm)
> +{
> +	return xe_rpm_get(drm);
> +}
> +
> +static struct ref_tracker *xe_rpm_get_if_in_use(const struct drm_device *drm)
> +{
> +	return xe_pm_runtime_get_if_in_use(to_xe_device(drm)) ? INTEL_WAKEREF_DEF : NULL;
> +}
> +
> +static struct ref_tracker *xe_rpm_get_noresume(const struct drm_device *drm)
> +{
> +	xe_pm_runtime_get_noresume(to_xe_device(drm));
> +
> +	return INTEL_WAKEREF_DEF;
> +}
> +
> +static void xe_rpm_put(const struct drm_device *drm, struct ref_tracker *wakeref)
> +{
> +	if (wakeref)
> +		xe_pm_runtime_put(to_xe_device(drm));
> +}
> +
> +static void xe_rpm_put_raw(const struct drm_device *drm, struct ref_tracker *wakeref)
> +{
> +	xe_rpm_put(drm, wakeref);
> +}
> +
> +static void xe_rpm_put_unchecked(const struct drm_device *drm)
> +{
> +	xe_pm_runtime_put(to_xe_device(drm));
> +}
> +
> +static bool xe_rpm_suspended(const struct drm_device *drm)
> +{
> +	struct xe_device *xe = to_xe_device(drm);
> +
> +	return pm_runtime_suspended(xe->drm.dev);
> +}
> +
> +static void xe_rpm_assert_held(const struct drm_device *drm)
> +{
> +	/* FIXME */
> +}
> +
> +static void xe_rpm_assert_block(const struct drm_device *drm)
> +{
> +	/* FIXME */
> +}
> +
> +static void xe_rpm_assert_unblock(const struct drm_device *drm)
> +{
> +	/* FIXME */
> +}
> +
> +static struct intel_display_rpm rpm = {

const

> +	.get = xe_rpm_get,
> +	.get_raw = xe_rpm_get_raw,
> +	.get_if_in_use = xe_rpm_get_if_in_use,
> +	.get_noresume = xe_rpm_get_noresume,
> +	.put = xe_rpm_put,
> +	.put_raw = xe_rpm_put_raw,
> +	.put_unchecked = xe_rpm_put_unchecked,
> +	.suspended = xe_rpm_suspended,
> +	.assert_held = xe_rpm_assert_held,
> +	.assert_block = xe_rpm_assert_block,
> +	.assert_unblock = xe_rpm_assert_unblock
> +};


Same here about placement. Maybe we reuse xe_display_rpm.c for this,
since in xe unlike in i915 display can be compiled out.

BR,
Jani.


> +
>  static const struct intel_display_parent_interface parent = {
> +	.rpm = &rpm,
>  };
>  
>  /**

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-10-22  9:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  8:55 [PATCH 0/6] Use display parent interface for runtime pm Jouni Högander
2025-10-22  8:55 ` [PATCH 1/6] drm/{i915, xe}/display: pass parent interface to display probe Jouni Högander
2025-10-22  9:17   ` [PATCH 1/6] drm/{i915,xe}/display: " Jani Nikula
2025-10-23  7:18     ` Jani Nikula
2025-10-22  8:55 ` [PATCH 2/6] drm/{i915, xe}/display: Add display runtime pm parent interface Jouni Högander
2025-10-22  9:22   ` Jani Nikula
2025-10-22  8:55 ` [PATCH 3/6] drm/i915/display: Runtime pm wrappers for display " Jouni Högander
2025-10-22  9:27   ` Jani Nikula
2025-10-22  8:55 ` [PATCH 4/6] drm/xe/display: " Jouni Högander
2025-10-22  9:29   ` Jani Nikula [this message]
2025-10-22  8:55 ` [PATCH 5/6] drm/i915/display: Use display parent interface for i915 runtime pm Jouni Högander
2025-10-22  9:35   ` Jani Nikula
2025-10-22  8:55 ` [PATCH 6/6] drm/xe/display: Use display parent interface for xe " Jouni Högander
2025-10-22  9:36   ` Jani Nikula
2025-10-22  9:52 ` ✓ i915.CI.BAT: success for Use display parent interface for " Patchwork
2025-10-22 12:22 ` ✗ 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=05cda4146015ff0d939f4e2656cde4f30087d71c@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --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