From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: [PATCH 0/3] drm/i915/dmc_wl: Track pipe interrupt registers
Date: Fri, 3 Jan 2025 14:41:34 -0300 [thread overview]
Message-ID: <20250103174223.58140-1-gustavo.sousa@intel.com> (raw)
Pipe interrupt registers live in their respective pipes' power wells,
which are below PG0. That means that they must also be tracked as
registers that are powered-off during dynamic DC states.
For that, we first convert the display IRQ code to use display-specific
MMIO functions so that DMC wakelock checks are properly done and then
add the range for pipe interrupts in the table checked by the DMC
wakelock code.
This series fixes vblank timeouts that were happening due to PIPE
interrupt registers being accessed without the DMC wakelock.
Gustavo Sousa (3):
drm/i915/display: Use display MMIO functions in intel_display_irq.c
drm/i915/display: Wrap IRQ-specific uncore functions
drm/i915/dmc_wl: Track pipe interrupt registers
drivers/gpu/drm/i915/display/intel_de.h | 43 +++
.../gpu/drm/i915/display/intel_display_irq.c | 307 +++++++++---------
drivers/gpu/drm/i915/display/intel_dmc_wl.c | 1 +
3 files changed, 205 insertions(+), 146 deletions(-)
--
2.47.1
next reply other threads:[~2025-01-03 17:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 17:41 Gustavo Sousa [this message]
2025-01-03 17:41 ` [PATCH 1/3] drm/i915/display: Use display MMIO functions in intel_display_irq.c Gustavo Sousa
2025-01-09 7:03 ` Hogander, Jouni
2025-01-03 17:41 ` [PATCH 2/3] drm/i915/display: Wrap IRQ-specific uncore functions Gustavo Sousa
2025-01-07 9:16 ` Jani Nikula
2025-01-13 20:51 ` Gustavo Sousa
2025-01-03 17:41 ` [PATCH 3/3] drm/i915/dmc_wl: Track pipe interrupt registers Gustavo Sousa
2025-01-09 7:07 ` Hogander, Jouni
2025-01-03 18:30 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-03 18:31 ` ✓ CI.checkpatch: " Patchwork
2025-01-03 18:32 ` ✓ CI.KUnit: " Patchwork
2025-01-03 18:50 ` ✓ CI.Build: " Patchwork
2025-01-03 18:52 ` ✓ CI.Hooks: " Patchwork
2025-01-03 18:54 ` ✗ CI.checksparse: warning " Patchwork
2025-01-03 19:19 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-04 2:30 ` ✗ 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=20250103174223.58140-1-gustavo.sousa@intel.com \
--to=gustavo.sousa@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