From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
linux-amlogic@lists.infradead.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org,
Arseniy Krasnov <avkrasnov@salutedevices.com>
Subject: Re: [PATCH] ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT
Date: Tue, 13 Aug 2024 17:22:43 +0200 [thread overview]
Message-ID: <20240813152243.2H3-mnx5@linutronix.de> (raw)
In-Reply-To: <172356023429.57695.4053614993109219592.b4-ty@kernel.org>
On 2024-08-13 15:43:54 [+0100], Mark Brown wrote:
> On Tue, 06 Aug 2024 12:27:03 +0200, Jerome Brunet wrote:
> > With PREEMPT_RT enabled, spinlocks become preemptible.
> > This is usually not a problem with spinlocks used in IRQ context since
> > IRQ handlers get threaded. However, if IRQF_ONESHOT is set, the upper half
> > of a threaded irq handler won't be threaded and this causes scheduling
> > problems if spinlocks are used in the upper half, like with regmap when
> > '.fast_io' is set.
> >
> > [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
>
> Thanks!
>
> [1/1] ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT
> commit: 5003d0ce5c7da3a02c0aff771f516f99731e7390
Didn't you already apply v2 of this?
Sebastian
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2024-08-13 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 10:27 [PATCH] ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT Jerome Brunet
2024-08-06 12:36 ` Sebastian Andrzej Siewior
2024-08-13 14:43 ` Mark Brown
2024-08-13 15:22 ` Sebastian Andrzej Siewior [this message]
2024-08-13 17:03 ` Mark Brown
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=20240813152243.2H3-mnx5@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=alsa-devel@alsa-project.org \
--cc=avkrasnov@salutedevices.com \
--cc=broonie@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.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