From: Maarten Lankhorst <dev@lankhorst.se>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
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, clrkwllms@kernel.org,
rostedt@goodmis.org, jerome.anand@intel.com,
pierre-louis.bossart@linux.dev, tiwai@suse.de,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev, jianhao.xu@seu.edu.cn,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/audio: use generic_handle_irq_safe() for LPE audio irq
Date: Fri, 29 May 2026 11:50:18 +0200 [thread overview]
Message-ID: <2023cf0e-85a8-4128-857d-cae806ff0e58@lankhorst.se> (raw)
In-Reply-To: <20260529074816.k1K16jyy@linutronix.de>
Hey,
Den 2026-05-29 kl. 09:48, skrev Sebastian Andrzej Siewior:
> On 2026-05-28 23:45:51 [+0800], Runyu Xiao wrote:
>> intel_lpe_audio_irq_handler() forwards the LPE audio child IRQ from the
>> i915 parent IRQ path with generic_handle_irq(). The forwarded child top
>> half is not an independent hardirq entry point; it inherits the context
>> of the outer i915 interrupt dispatch path.
> …
>
> This looks very familiar and is work in progress
> https://lore.kernel.org/all/20260310115709.2276203-16-dev@lankhorst.se/
>
> Maarten, where do we stand on the i915 series?
>
>> Fixes: eef57324d926 ("drm/i915: setup bridge for HDMI LPE audio driver")
>> Cc: stable@vger.kernel.org
>
> No stable fix needed because i915 can not be turned on PREEMPT_RT.
>
> Sebastian
It's been absolutely rock stable since the last time I submitted it.
I've been using it on my local machine, and the amount of times >100us
(evasion failed) with and without PREEMPT_RT are identical with
the vblank changes.
It still applies cleanly when rebasing.
The vblank patches are the most involved change, and they ensure that
absolutely no lock contention happens in the critical path with irqs off.
Unfortunately the status is still same as the time I submitted it before it,
and pending reviews on the series.
Kind regards,
~Maarten Lankhorst
next prev parent reply other threads:[~2026-05-29 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 15:45 [PATCH] drm/i915/audio: use generic_handle_irq_safe() for LPE audio irq Runyu Xiao
2026-05-29 7:48 ` Sebastian Andrzej Siewior
2026-05-29 9:50 ` Maarten Lankhorst [this message]
2026-05-29 12:21 ` Sebastian Andrzej Siewior
2026-05-29 14:25 ` Runyu Xiao
2026-05-29 15:21 ` Jani Nikula
2026-05-31 15:23 ` Runyu Xiao
2026-05-31 15:31 ` [PATCH v2] " Runyu Xiao
2026-06-01 9:04 ` Sebastian Andrzej Siewior
2026-06-04 4:47 ` Claude review: " 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=2023cf0e-85a8-4128-857d-cae806ff0e58@lankhorst.se \
--to=dev@lankhorst.se \
--cc=airlied@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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=linux-rt-devel@lists.linux.dev \
--cc=pierre-louis.bossart@linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=rostedt@goodmis.org \
--cc=runyu.xiao@seu.edu.cn \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=tursulin@ursulin.net \
/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