From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
imre.deak@intel.com
Subject: Re: [PATCH 22/24] drm/i915: add intel_display_driver_pm_runtime*() functions
Date: Fri, 29 May 2026 22:05:01 +0300 [thread overview]
Message-ID: <ahnjXXO-h7NYocBy@intel.com> (raw)
In-Reply-To: <9417d53a338b5a14b9bf50cb8585b13b7379a6d3.1780051905.git.jani.nikula@intel.com>
On Fri, May 29, 2026 at 02:04:06PM +0300, Jani Nikula wrote:
> Add new functions intel_display_driver_pm_runtime_suspend(),
> intel_display_driver_pm_runtime_suspend_late(),
> intel_display_driver_pm_runtime_resume_early(), and
> intel_display_driver_pm_runtime_resume(). Initially, only migrate i915,
> as there are some differences with xe that will be addressed later.
>
> There are a few functional changes, which should be benign:
>
> - i915_pm_runtime_suspend() moves assert_forcewakes_inactive() call
> before opregion calls.
>
> - i915_pm_runtime_resume() moves intel_opregion_notify_adapter() call
> slightly later.
>
> In the interest of not introducing more severe functional changes, the
> calls become slightly asymmetric. We might want to address this later.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> .../drm/i915/display/intel_display_driver.c | 56 +++++++++++++++++++
> .../drm/i915/display/intel_display_driver.h | 5 ++
> drivers/gpu/drm/i915/i915_driver.c | 44 ++-------------
> 3 files changed, 65 insertions(+), 40 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_driver.c b/drivers/gpu/drm/i915/display/intel_display_driver.c
> index 84807a9bff2b..a27ddf21b08b 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_driver.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_driver.c
> @@ -884,3 +884,59 @@ void intel_display_driver_pm_resume(struct intel_display *display)
>
> intel_display_power_enable(display);
> }
> +
> +void intel_display_driver_pm_runtime_suspend(struct intel_display *display)
> +{
> + intel_display_power_runtime_suspend(display);
> +}
> +
> +void intel_display_driver_pm_runtime_suspend_late(struct intel_display *display)
> +{
> + /*
> + * FIXME: We really should find a document that references the arguments
> + * used below!
> + */
> + if (display->platform.broadwell) {
> + /*
> + * On Broadwell, if we use PCI_D1 the PCH DDI ports will stop
> + * being detected, and the call we do at i915_pm_runtime_resume()
> + * won't be able to restore them. Since PCI_D3hot matches the
> + * actual specification and appears to be working, use it.
> + */
> + intel_opregion_notify_adapter(display, PCI_D3hot);
> + } else {
> + /*
> + * current versions of firmware which depend on this opregion
> + * notification have repurposed the D1 definition to mean
> + * "runtime suspended" vs. what you would normally expect (D3)
> + * to distinguish it from notifications that might be sent via
> + * the suspend path.
> + */
> + intel_opregion_notify_adapter(display, PCI_D1);
> + }
> +
> + if (!display->platform.valleyview && !display->platform.cherryview)
> + intel_hpd_poll_enable(display);
> +}
> +
> +void intel_display_driver_pm_runtime_resume_early(struct intel_display *display)
> +{
> + intel_opregion_notify_adapter(display, PCI_D0);
> +
> + intel_display_power_runtime_resume(display);
> +}
> +
> +void intel_display_driver_pm_runtime_resume(struct intel_display *display)
> +{
> + /*
> + * On VLV/CHV display interrupts are part of the display
> + * power well, so hpd is reinitialized from there. For
> + * everyone else do it here.
> + */
> + if (!display->platform.valleyview && !display->platform.cherryview) {
> + intel_hpd_init(display);
> + intel_hpd_poll_disable(display);
> + }
> +
> + skl_watermark_ipc_update(display);
> +}
> diff --git a/drivers/gpu/drm/i915/display/intel_display_driver.h b/drivers/gpu/drm/i915/display/intel_display_driver.h
> index 7eca3d17dd82..1b494337d629 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_driver.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_driver.h
> @@ -43,5 +43,10 @@ void intel_display_driver_suspend_access(struct intel_display *display);
> void intel_display_driver_resume_access(struct intel_display *display);
> bool intel_display_driver_check_access(struct intel_display *display);
>
> +void intel_display_driver_pm_runtime_suspend(struct intel_display *display);
> +void intel_display_driver_pm_runtime_suspend_late(struct intel_display *display);
> +void intel_display_driver_pm_runtime_resume_early(struct intel_display *display);
> +void intel_display_driver_pm_runtime_resume(struct intel_display *display);
> +
> #endif /* __INTEL_DISPLAY_DRIVER_H__ */
>
> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> index 6b9e1b268a89..519a519d2d96 100644
> --- a/drivers/gpu/drm/i915/i915_driver.c
> +++ b/drivers/gpu/drm/i915/i915_driver.c
> @@ -1521,7 +1521,7 @@ static int i915_pm_runtime_suspend(struct device *kdev)
> for_each_gt(gt, dev_priv, i)
> intel_uncore_suspend(gt->uncore);
>
> - intel_display_power_runtime_suspend(display);
> + intel_display_driver_pm_runtime_suspend(display);
>
> ret = vlv_suspend_complete(dev_priv);
> if (ret) {
> @@ -1555,33 +1555,9 @@ static int i915_pm_runtime_suspend(struct device *kdev)
> if (root_pdev)
> pci_d3cold_disable(root_pdev);
>
> - /*
> - * FIXME: We really should find a document that references the arguments
> - * used below!
> - */
> - if (IS_BROADWELL(dev_priv)) {
> - /*
> - * On Broadwell, if we use PCI_D1 the PCH DDI ports will stop
> - * being detected, and the call we do at i915_pm_runtime_resume()
> - * won't be able to restore them. Since PCI_D3hot matches the
> - * actual specification and appears to be working, use it.
> - */
> - intel_opregion_notify_adapter(display, PCI_D3hot);
> - } else {
> - /*
> - * current versions of firmware which depend on this opregion
> - * notification have repurposed the D1 definition to mean
> - * "runtime suspended" vs. what you would normally expect (D3)
> - * to distinguish it from notifications that might be sent via
> - * the suspend path.
> - */
> - intel_opregion_notify_adapter(display, PCI_D1);
> - }
> -
> assert_forcewakes_inactive(&dev_priv->uncore);
>
> - if (!IS_VALLEYVIEW(dev_priv) && !IS_CHERRYVIEW(dev_priv))
> - intel_hpd_poll_enable(display);
> + intel_display_driver_pm_runtime_suspend_late(display);
>
> drm_dbg(&dev_priv->drm, "Device suspended\n");
> return 0;
> @@ -1605,8 +1581,6 @@ static int i915_pm_runtime_resume(struct device *kdev)
> drm_WARN_ON_ONCE(&dev_priv->drm, atomic_read(&rpm->wakeref_count));
> disable_rpm_wakeref_asserts(rpm);
>
> - intel_opregion_notify_adapter(display, PCI_D0);
> -
> root_pdev = pcie_find_root_port(pdev);
> if (root_pdev)
> pci_d3cold_enable(root_pdev);
> @@ -1615,7 +1589,7 @@ static int i915_pm_runtime_resume(struct device *kdev)
> drm_dbg(&dev_priv->drm,
> "Unclaimed access during suspend, bios?\n");
>
> - intel_display_power_runtime_resume(display);
> + intel_display_driver_pm_runtime_resume_early(display);
>
> ret = vlv_resume_prepare(dev_priv, true);
>
> @@ -1633,17 +1607,7 @@ static int i915_pm_runtime_resume(struct device *kdev)
>
> intel_pxp_runtime_resume(dev_priv->pxp);
>
> - /*
> - * On VLV/CHV display interrupts are part of the display
> - * power well, so hpd is reinitialized from there. For
> - * everyone else do it here.
> - */
> - if (!IS_VALLEYVIEW(dev_priv) && !IS_CHERRYVIEW(dev_priv)) {
> - intel_hpd_init(display);
> - intel_hpd_poll_disable(display);
> - }
> -
> - skl_watermark_ipc_update(display);
> + intel_display_driver_pm_runtime_resume(display);
>
> enable_rpm_wakeref_asserts(rpm);
>
> --
> 2.47.3
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-05-29 19:05 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 11:03 [PATCH 00/24] drm/{i915, xe}: display (runtime) suspend/resume/shutdown unification Jani Nikula
2026-05-29 11:03 ` [PATCH 01/24] drm/i915: Keep display IRQs enabled for encoder suspend/shutdown Jani Nikula
2026-05-29 11:03 ` [PATCH 02/24] drm/i915/xe: Enable HPD polling later during system resume Jani Nikula
2026-05-29 11:03 ` [PATCH 03/24] drm/i915: add flush_workqueue(display->wq.cleanup) on shutdown Jani Nikula
2026-05-29 13:07 ` Ville Syrjälä
2026-05-29 11:03 ` [PATCH 04/24] drm/xe/display: remove intel_display_flush_cleanup_work() calls on suspend/shutdown Jani Nikula
2026-05-29 13:18 ` Ville Syrjälä
2026-05-29 11:03 ` [PATCH 05/24] drm/xe/display: drop duplicate intel_dp_mst_suspend() call Jani Nikula
2026-05-29 13:18 ` Ville Syrjälä
2026-05-29 11:03 ` [PATCH 06/24] drm/i915/display: add "pm" to intel_display_driver_{suspend, resume}() names Jani Nikula
2026-05-29 13:30 ` [PATCH 06/24] drm/i915/display: add "pm" to intel_display_driver_{suspend,resume}() names Ville Syrjälä
2026-05-29 11:03 ` [PATCH 07/24] drm/xe/display: rename xe_display_pm_shutdown*() to xe_display_shutdown*() Jani Nikula
2026-05-29 13:30 ` Ville Syrjälä
2026-05-29 11:03 ` [PATCH 08/24] drm/xe/display: relocate the xe_display_shutdown*() functions Jani Nikula
2026-06-02 7:22 ` Michał Grzelak
2026-05-29 11:03 ` [PATCH 09/24] drm/xe/display: relocate the xe_display_pm_runtime_*() functions Jani Nikula
2026-06-02 7:23 ` Michał Grzelak
2026-05-29 11:03 ` [PATCH 10/24] drm/{i915, xe}: move more calls inside intel_display_driver_pm_suspend() Jani Nikula
2026-05-29 13:36 ` [PATCH 10/24] drm/{i915,xe}: " Ville Syrjälä
2026-05-29 11:03 ` [PATCH 11/24] drm/{i915, xe}: move more calls inside intel_display_driver_pm_resume() Jani Nikula
2026-05-29 13:38 ` [PATCH 11/24] drm/{i915,xe}: " Ville Syrjälä
2026-05-29 11:03 ` [PATCH 12/24] drm/{i915, xe}: add intel_display_driver_pm_{suspend_late, resume_early}() Jani Nikula
2026-05-29 13:39 ` [PATCH 12/24] drm/{i915,xe}: add intel_display_driver_pm_{suspend_late,resume_early}() Ville Syrjälä
2026-05-29 11:03 ` [PATCH 13/24] drm/{i915, xe}: move more calls inside intel_display_driver_{register, unregister}() Jani Nikula
2026-05-29 14:04 ` [PATCH 13/24] drm/{i915,xe}: move more calls inside intel_display_driver_{register,unregister}() Ville Syrjälä
2026-05-29 11:03 ` [PATCH 14/24] drm/{i915, xe}: add intel_display_driver_shutdown_late() Jani Nikula
2026-05-29 14:05 ` [PATCH 14/24] drm/{i915,xe}: " Ville Syrjälä
2026-05-29 11:03 ` [PATCH 15/24] drm/i915: add intel_display_driver_shutdown() Jani Nikula
2026-05-29 17:57 ` Ville Syrjälä
2026-05-29 11:04 ` [PATCH 16/24] drm/i915/display: deduplicate suspend and shutdown a bit Jani Nikula
2026-05-29 17:59 ` Ville Syrjälä
2026-05-29 11:04 ` [PATCH 17/24] drm/xe/display: use intel_display_driver_pm_shutdown() Jani Nikula
2026-05-29 18:02 ` Ville Syrjälä
2026-05-29 11:04 ` [PATCH 18/24] drm/{i915, xe}: move more stuff to __intel_display_driver_pm_suspend() Jani Nikula
2026-05-29 18:03 ` [PATCH 18/24] drm/{i915,xe}: " Ville Syrjälä
2026-05-29 11:04 ` [PATCH 19/24] drm/{i915, xe}: make intel_dmc_suspend() part of display suspend/shutdown calls Jani Nikula
2026-05-29 14:16 ` [PATCH 19/24] drm/{i915,xe}: " Ville Syrjälä
2026-06-01 8:14 ` Imre Deak
2026-05-29 11:04 ` [PATCH 20/24] drm/{i915, xe}: move intel_opregion_suspend() to intel_display_driver_pm_suspend_late() Jani Nikula
2026-05-29 14:42 ` [PATCH 20/24] drm/{i915,xe}: " Ville Syrjälä
2026-05-29 11:04 ` [PATCH 21/24] drm/{i915, xe}: keep moving stuff to intel_display_driver_pm_resume() Jani Nikula
2026-05-29 18:45 ` [PATCH 21/24] drm/{i915,xe}: " Ville Syrjälä
2026-05-29 11:04 ` [PATCH 22/24] drm/i915: add intel_display_driver_pm_runtime*() functions Jani Nikula
2026-05-29 19:05 ` Ville Syrjälä [this message]
2026-05-29 11:04 ` [PATCH 23/24] drm/xe/display: separate d3cold handling from xe_display_pm_runtime_suspend_late() Jani Nikula
2026-05-29 19:05 ` Ville Syrjälä
2026-05-29 11:04 ` [PATCH 24/24] drm/xe/display: unify runtime suspend/resume with i915 for non-d3cold Jani Nikula
2026-05-29 19:12 ` Ville Syrjälä
2026-06-05 16:04 ` Jani Nikula
2026-05-29 11:13 ` ✓ CI.KUnit: success for drm/{i915, xe}: display (runtime) suspend/resume/shutdown unification Patchwork
2026-05-29 11:59 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-05-29 14:07 ` ✗ Xe.CI.FULL: " 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=ahnjXXO-h7NYocBy@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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