From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Maarten Lankhorst <dev@lankhorst.se>,
Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH 01/11] drm/i915/display: Fix intel_lpe_audio_irq_handler for PREEMPT-RT
Date: Fri, 12 Dec 2025 14:02:07 +0100 [thread overview]
Message-ID: <20251212130205.963029-14-dev@lankhorst.se> (raw)
In-Reply-To: <20251212130205.963029-13-dev@lankhorst.se>
The LPE audio interrupt comes from the i915 interrupt handler. It
should be in irq disabled context.
With PREEMPT_RT enabled, the IRQ handler is threaded.
Because intel_lpe_audio_irq_handler() may be called in threaded IRQ context,
generic_handle_irq_safe API disables the interrupts before calling LPE's
interrupt top half handler.
This fixes braswell audio issues with RT enabled.
Signed-off-by: Maarten Lankhorst <dev@lankhorst.se>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/i915/display/intel_lpe_audio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_lpe_audio.c b/drivers/gpu/drm/i915/display/intel_lpe_audio.c
index 5b41abe1c64d5..172c0062237eb 100644
--- a/drivers/gpu/drm/i915/display/intel_lpe_audio.c
+++ b/drivers/gpu/drm/i915/display/intel_lpe_audio.c
@@ -262,7 +262,7 @@ void intel_lpe_audio_irq_handler(struct intel_display *display)
if (!HAS_LPE_AUDIO(display))
return;
- ret = generic_handle_irq(display->audio.lpe.irq);
+ ret = generic_handle_irq_safe(display->audio.lpe.irq);
if (ret)
drm_err_ratelimited(display->drm,
"error handling LPE audio irq: %d\n", ret);
--
2.51.0
next prev parent reply other threads:[~2025-12-12 13:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 13:02 [PATCH 00/11] drm/i915/display: All patches to make PREEMPT_RT work on xe Maarten Lankhorst
2025-12-12 13:02 ` Maarten Lankhorst [this message]
2025-12-12 13:02 ` [PATCH 02/11] drm/i915/display: Make get_vblank_counter use intel_de_read_fw() Maarten Lankhorst
2025-12-12 13:02 ` [PATCH 03/11] drm/i915/display: Use intel_de_write_fw in intel_pipe_fastset Maarten Lankhorst
2025-12-12 13:02 ` [PATCH 04/11] drm/i915/display: Make set_pipeconf use the fw variants Maarten Lankhorst
2025-12-12 13:02 ` [PATCH 05/11] drm/i915/display: Move vblank put until after critical section Maarten Lankhorst
2025-12-12 13:02 ` [PATCH 06/11] drm/i915/display: Remove locking from intel_vblank_evade " Maarten Lankhorst
2025-12-12 13:02 ` [PATCH 07/11] drm/i915/display: Handle vlv dsi workaround in scanline_in_safe_range too Maarten Lankhorst
2025-12-12 13:02 ` [PATCH 08/11] drm/i915/display: Make icl_dsi_frame_update use _fw too Maarten Lankhorst
2025-12-12 13:02 ` [PATCH 09/11] drm/i915/display: Enable interrupts earlier on PREEMPT_RT Maarten Lankhorst
2025-12-12 13:02 ` [PATCH 10/11] drm/i915: Use preempt_disable/enable_rt() where recommended Maarten Lankhorst
2025-12-12 13:02 ` [CI-ONLY PATCH 11/11] PREEMPT_RT injection Maarten Lankhorst
2025-12-12 13:11 ` ✗ CI.checkpatch: warning for drm/i915/display: All patches to make PREEMPT_RT work on xe Patchwork
2025-12-12 13:12 ` ✓ CI.KUnit: success " Patchwork
2025-12-12 13:26 ` ✗ CI.checksparse: warning " Patchwork
2025-12-12 14:15 ` ✗ Xe.CI.BAT: 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=20251212130205.963029-14-dev@lankhorst.se \
--to=dev@lankhorst.se \
--cc=bigeasy@linutronix.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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