From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: [PATCH 0/6] Use display parent interface for runtime pm
Date: Wed, 22 Oct 2025 11:55:42 +0300 [thread overview]
Message-ID: <20251022085548.876150-1-jouni.hogander@intel.com> (raw)
Add struct intel_display_parent_interface which is supposed to contain
function pointers passed at display probe. This is supposed to allow
differing implementations between i915 and xe drivers.
Add runtime pm as an example and first set of functions using this new
mechanism. Pass own implementations of runtime from i915 and xe
drivers during probe.
Jani Nikula (1):
drm/{i915,xe}/display: pass parent interface to display probe
Jouni Högander (5):
drm/{i915,xe}/display: Add display runtime pm parent interface
drm/i915/display: Runtime pm wrappers for display parent interface
drm/xe/display: Runtime pm wrappers for display parent interface
drm/i915/display: Use display parent interface for i915 runtime pm
drm/xe/display: Use display parent interface for xe runtime pm
.../gpu/drm/i915/display/intel_display_core.h | 4 +
.../drm/i915/display/intel_display_device.c | 5 +-
.../drm/i915/display/intel_display_device.h | 4 +-
.../gpu/drm/i915/display/intel_display_rpm.c | 43 +++++----
drivers/gpu/drm/i915/display/intel_fb.c | 1 +
.../drm/i915/display/skl_universal_plane.c | 1 +
drivers/gpu/drm/i915/i915_driver.c | 88 ++++++++++++++++++-
drivers/gpu/drm/i915/i915_driver.h | 2 +
.../gpu/drm/i915/selftests/mock_gem_device.c | 4 +-
drivers/gpu/drm/xe/Makefile | 2 +-
.../gpu/drm/xe/compat-i915-headers/i915_drv.h | 1 -
drivers/gpu/drm/xe/display/xe_display.c | 82 ++++++++++++++++-
drivers/gpu/drm/xe/display/xe_display_rpm.c | 73 ---------------
include/drm/intel/display_parent_interface.h | 44 ++++++++++
14 files changed, 255 insertions(+), 99 deletions(-)
delete mode 100644 drivers/gpu/drm/xe/display/xe_display_rpm.c
create mode 100644 include/drm/intel/display_parent_interface.h
--
2.43.0
next reply other threads:[~2025-10-22 8:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 8:55 Jouni Högander [this message]
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
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:41 ` ✗ CI.checkpatch: warning for Use display parent interface for " Patchwork
2025-10-22 9:42 ` ✓ CI.KUnit: success " Patchwork
2025-10-22 10:00 ` ✗ CI.checksparse: warning " Patchwork
2025-10-22 11:02 ` ✓ Xe.CI.BAT: success " Patchwork
2025-10-22 13:13 ` ✗ Xe.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=20251022085548.876150-1-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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