From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, rodrigo.vivi@intel.com,
ville.syrjala@linux.intel.com
Subject: [PATCH 0/4] drm/{i915,xe}: unify runtime pm calls
Date: Mon, 15 Jun 2026 15:40:44 +0300 [thread overview]
Message-ID: <cover.1781527161.git.jani.nikula@intel.com> (raw)
Unify the runtime pm hooks for i915 and xe, apart from the xe special
d3cold handling, which gets separated from the rest.
Jani Nikula (4):
drm/i915: add intel_display_driver_pm_runtime*() functions
drm/{i915,xe}: add new
intel_display_driver_runtime_pm_{enable,disable}()
drm/xe/display: separate d3cold handling from
xe_display_pm_runtime_suspend_late()
drm/xe/display: unify runtime suspend/resume with i915 for non-d3cold
.../drm/i915/display/intel_display_driver.c | 66 +++++++++++++++++++
.../drm/i915/display/intel_display_driver.h | 8 +++
drivers/gpu/drm/i915/i915_driver.c | 48 ++------------
drivers/gpu/drm/xe/display/xe_display.c | 28 ++++----
4 files changed, 93 insertions(+), 57 deletions(-)
--
2.47.3
next reply other threads:[~2026-06-15 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 12:40 Jani Nikula [this message]
2026-06-15 12:40 ` [PATCH 1/4] drm/i915: add intel_display_driver_pm_runtime*() functions Jani Nikula
2026-06-15 12:40 ` [PATCH 2/4] drm/{i915, xe}: add new intel_display_driver_runtime_pm_{enable, disable}() Jani Nikula
2026-06-15 12:40 ` [PATCH 3/4] drm/xe/display: separate d3cold handling from xe_display_pm_runtime_suspend_late() Jani Nikula
2026-06-15 12:40 ` [PATCH 4/4] drm/xe/display: unify runtime suspend/resume with i915 for non-d3cold Jani Nikula
2026-06-15 12:48 ` ✓ CI.KUnit: success for drm/{i915,xe}: unify runtime pm calls Patchwork
2026-06-15 13:46 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-06-15 14:41 ` ✗ Xe.CI.FULL: " Patchwork
2026-06-15 15:10 ` ✓ i915.CI.BAT: success " 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=cover.1781527161.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.