Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH 2/2] drm/xe: Add missing HPD interrupt enabling during non-d3cold RPM resume
Date: Mon,  7 Oct 2024 17:05:31 +0300	[thread overview]
Message-ID: <20241007140531.1044630-2-imre.deak@intel.com> (raw)
In-Reply-To: <20241007140531.1044630-1-imre.deak@intel.com>

Atm the display HPD interrupts that got disabled during runtime
suspend, are re-enabled only if d3cold is enabled. Fix things by
also re-enabling the interrupts if d3cold is disabled.

Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
 drivers/gpu/drm/xe/display/xe_display.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
index cb2449b7921ac..695c27ac6b0f8 100644
--- a/drivers/gpu/drm/xe/display/xe_display.c
+++ b/drivers/gpu/drm/xe/display/xe_display.c
@@ -486,6 +486,7 @@ void xe_display_pm_runtime_resume(struct xe_device *xe)
 		return;
 	}
 
+	intel_hpd_init(xe);
 	intel_hpd_poll_disable(xe);
 }
 
-- 
2.44.2


  reply	other threads:[~2024-10-07 14:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 14:05 [PATCH 1/2] drm/xe: Separate the d3cold and non-d3cold runtime PM handling Imre Deak
2024-10-07 14:05 ` Imre Deak [this message]
2024-10-07 18:29   ` [PATCH 2/2] drm/xe: Add missing HPD interrupt enabling during non-d3cold RPM resume Cavitt, Jonathan
2024-10-07 18:46     ` Imre Deak
2024-10-07 18:52       ` Rodrigo Vivi
2024-10-08 15:33         ` Imre Deak
2024-10-08 20:21           ` Rodrigo Vivi
2024-10-07 18:28 ` [PATCH 1/2] drm/xe: Separate the d3cold and non-d3cold runtime PM handling Cavitt, Jonathan
2024-10-07 18:45   ` Imre Deak
2024-10-07 19:24 ` ✓ CI.Patch_applied: success for series starting with [1/2] " Patchwork
2024-10-07 19:24 ` ✓ CI.checkpatch: " Patchwork
2024-10-07 19:25 ` ✓ CI.KUnit: " Patchwork
2024-10-07 19:37 ` ✓ CI.Build: " Patchwork
2024-10-07 19:39 ` ✓ CI.Hooks: " Patchwork
2024-10-07 19:41 ` ✓ CI.checksparse: " Patchwork
2024-10-07 20:13 ` ✓ CI.BAT: " Patchwork
2024-10-08  8:27 ` ✗ 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=20241007140531.1044630-2-imre.deak@intel.com \
    --to=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@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