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 2/6] drm/{i915, xe}/display: Add display runtime pm parent interface
Date: Wed, 22 Oct 2025 12:22:39 +0300 [thread overview]
Message-ID: <4aba6377fa0f65d0f93e34f5539e58cfdbae4947@intel.com> (raw)
In-Reply-To: <20251022085548.876150-3-jouni.hogander@intel.com>
On Wed, 22 Oct 2025, Jouni Högander <jouni.hogander@intel.com> wrote:
> We have differing implementations for display runtime pm in i915 and xe
> drivers. Add struct of function pointers into display_parent_interface
> which will contain used implementation of runtime pm.
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> include/drm/intel/display_parent_interface.h | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/include/drm/intel/display_parent_interface.h b/include/drm/intel/display_parent_interface.h
> index 28c976815327a..7ad0a27d503c8 100644
> --- a/include/drm/intel/display_parent_interface.h
> +++ b/include/drm/intel/display_parent_interface.h
> @@ -8,6 +8,22 @@
>
> struct drm_device;
>
> +struct intel_display_rpm {
I'm wondering if it would better emphasize the point if we named these
structs with _interface suffix.
> + struct ref_tracker *(*get)(const struct drm_device *drm);
I think we should have the struct ref_tracker forward declaration above.
> + struct ref_tracker *(*get_raw)(const struct drm_device *drm);
> + struct ref_tracker *(*get_if_in_use)(const struct drm_device *drm);
> + struct ref_tracker *(*get_noresume)(const struct drm_device *drm);
> +
> + void (*put)(const struct drm_device *drm, struct ref_tracker *wakeref);
> + void (*put_raw)(const struct drm_device *drm, struct ref_tracker *wakeref);
> + void (*put_unchecked)(const struct drm_device *drm);
> +
> + bool (*suspended)(const struct drm_device *drm);
> + void (*assert_held)(const struct drm_device *drm);
> + void (*assert_block)(const struct drm_device *drm);
> + void (*assert_unblock)(const struct drm_device *drm);
> +};
> +
> /**
> * struct intel_display_parent_interface - services parent driver provides to display
> *
> @@ -21,6 +37,8 @@ struct drm_device;
> * check the optional pointers.
> */
> struct intel_display_parent_interface {
> + /* Runtime PM functions */
I think these should be kernel-doc comments, i.e. /** @rpm: ... */. They
can still be one-liners.
BR,
Jani.
> + const struct intel_display_rpm *rpm;
> };
>
> #endif
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-10-22 9:22 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 [this message]
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
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=4aba6377fa0f65d0f93e34f5539e58cfdbae4947@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