From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
rodrigo.vivi@intel.com
Subject: Re: [RESEND v2 0/8] drm/{i915,xe}: unify runtime pm calls
Date: Fri, 03 Jul 2026 15:36:47 +0300 [thread overview]
Message-ID: <aadf2fef6ec60c4eb935320cec96efb1921f679b@intel.com> (raw)
In-Reply-To: <akeNb7UeeFXMvbU8@intel.com>
On Fri, 03 Jul 2026, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Jul 01, 2026 at 04:52:58PM +0300, Jani Nikula wrote:
>> Resend of [1], which is v2 of [2].
>>
>> [1] https://lore.kernel.org/r/cover.1782311749.git.jani.nikula@intel.com
>> [2] https://lore.kernel.org/r/cover.1781527161.git.jani.nikula@intel.com
>>
>> Jani Nikula (8):
>> drm/i915: call intel_uncore_runtime_resume() for each gt
>> drm/i915: call intel_display_power_runtime_resume() on suspend error
>> path
>> drm/i915: move some display runtime suspend operations earlier
>> 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: add xe_display_pm_runtime_resume_early()
>> drm/xe/display: unify runtime suspend/resume with i915 for non-d3cold
>
> I got a bit sidetracked into the system suspend code and the
> somewhat tangled mess of gem/gt/uncore while looking at this,
> but all of that looks mostly separate from this.
Yes, there are more dragons to tame.
> For the series
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks a lot, pushed to din.
BR,
Jani.
>
>>
>> .../drm/i915/display/intel_display_driver.c | 71 +++++++++++++++++++
>> .../drm/i915/display/intel_display_driver.h | 8 +++
>> drivers/gpu/drm/i915/i915_driver.c | 58 ++++-----------
>> drivers/gpu/drm/xe/display/xe_display.c | 44 ++++++++----
>> drivers/gpu/drm/xe/display/xe_display.h | 1 +
>> drivers/gpu/drm/xe/xe_pm.c | 2 +
>> 6 files changed, 125 insertions(+), 59 deletions(-)
>>
>> --
>> 2.47.3
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-07-03 12:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 13:52 [RESEND v2 0/8] drm/{i915,xe}: unify runtime pm calls Jani Nikula
2026-07-01 13:52 ` [RESEND v2 1/8] drm/i915: call intel_uncore_runtime_resume() for each gt Jani Nikula
2026-07-01 13:53 ` [RESEND v2 2/8] drm/i915: call intel_display_power_runtime_resume() on suspend error path Jani Nikula
2026-07-01 19:59 ` Rodrigo Vivi
2026-07-01 13:53 ` [RESEND v2 3/8] drm/i915: move some display runtime suspend operations earlier Jani Nikula
2026-07-01 20:02 ` Rodrigo Vivi
2026-07-01 13:53 ` [RESEND v2 4/8] drm/i915: add intel_display_driver_pm_runtime*() functions Jani Nikula
2026-07-01 13:53 ` [RESEND v2 5/8] drm/{i915, xe}: add new intel_display_driver_runtime_pm_{enable, disable}() Jani Nikula
2026-07-01 13:53 ` [RESEND v2 6/8] drm/xe/display: separate d3cold handling from xe_display_pm_runtime_suspend_late() Jani Nikula
2026-07-01 13:53 ` [RESEND v2 7/8] drm/xe/display: add xe_display_pm_runtime_resume_early() Jani Nikula
2026-07-02 7:14 ` [PATCH v2] " Jani Nikula
2026-07-01 13:53 ` [RESEND v2 8/8] drm/xe/display: unify runtime suspend/resume with i915 for non-d3cold Jani Nikula
2026-07-01 15:36 ` ✗ CI.KUnit: failure for drm/{i915,xe}: unify runtime pm calls (rev3) Patchwork
2026-07-02 1:24 ` ✓ i915.CI.BAT: success " Patchwork
2026-07-02 7:22 ` ✓ CI.KUnit: success for drm/{i915,xe}: unify runtime pm calls (rev4) Patchwork
2026-07-02 8:27 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-02 8:33 ` ✓ i915.CI.BAT: " Patchwork
2026-07-03 0:10 ` ✗ i915.CI.Full: failure " Patchwork
2026-07-03 1:13 ` ✓ Xe.CI.FULL: success " Patchwork
2026-07-03 10:22 ` [RESEND v2 0/8] drm/{i915,xe}: unify runtime pm calls Ville Syrjälä
2026-07-03 12:36 ` Jani Nikula [this message]
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=aadf2fef6ec60c4eb935320cec96efb1921f679b@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.