From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Runyu Xiao <runyu.xiao@seu.edu.cn>
Cc: jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
joonas.lahtinen@linux.intel.com, tursulin@ursulin.net,
airlied@gmail.com, simona@ffwll.ch, dev@lankhorst.se,
matthew.brost@intel.com, uma.shankar@intel.com,
pierre-louis.bossart@linux.dev, jerome.anand@intel.com,
tiwai@suse.de, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
jianhao.xu@seu.edu.cn
Subject: Re: [PATCH v3] drm/i915/display: Fix intel_lpe_audio_irq_handler for PREEMPT-RT
Date: Tue, 2 Jun 2026 08:29:57 +0200 [thread overview]
Message-ID: <20260602062957.0Nbtw_yY@linutronix.de> (raw)
In-Reply-To: <20260602004515.1907422-1-runyu.xiao@seu.edu.cn>
On 2026-06-02 08:45:15 [+0800], Runyu Xiao wrote:
> From: Maarten Lankhorst <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>
> Reviewed-by: Uma Shankar <uma.shankar@intel.com>
> Signed-off-by: Runyu Xiao <runyu.xiao@seu.edu.cn>
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Sebastian
next prev parent reply other threads:[~2026-06-02 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 0:45 [PATCH v3] drm/i915/display: Fix intel_lpe_audio_irq_handler for PREEMPT-RT Runyu Xiao
2026-06-02 6:29 ` Sebastian Andrzej Siewior [this message]
2026-06-02 12:33 ` Maarten Lankhorst
2026-06-03 8:27 ` Jani Nikula
2026-06-03 13:28 ` Runyu Xiao
2026-06-04 3:25 ` Claude review: " Claude Code Review Bot
2026-06-04 3:25 ` Claude Code Review Bot
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=20260602062957.0Nbtw_yY@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=airlied@gmail.com \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jerome.anand@intel.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=runyu.xiao@seu.edu.cn \
--cc=simona@ffwll.ch \
--cc=tiwai@suse.de \
--cc=tursulin@ursulin.net \
--cc=uma.shankar@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