From: Jerome Brunet <jbrunet@baylibre.com>
To: Arseniy Krasnov <avkrasnov@salutedevices.com>,
Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
<alsa-devel@alsa-project.org>, <linux-sound@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel@sberdevices.ru>,
<oxffffaa@gmail.com>
Subject: Re: [PATCH v1] ASoC: meson: axg-fifo: set option to use raw spinlock
Date: Mon, 29 Jul 2024 16:15:31 +0200 [thread overview]
Message-ID: <1ja5i0wags.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20240729131652.3012327-1-avkrasnov@salutedevices.com> (Arseniy Krasnov's message of "Mon, 29 Jul 2024 16:16:52 +0300")
On Mon 29 Jul 2024 at 16:16, Arseniy Krasnov <avkrasnov@salutedevices.com> wrote:
> Raw spinlock is needed here, because with enabled PREEMPT_RT,
> spinlock_t become preemptible, but this regmap lock could be
> acquired in IRQ handler. Found by lockdep:
Assuming I understand the problem correctly, any driver with an IRQ and
using mmio regmaps would be subject to this problem, isn't it ?
That does not seems particularily specific to this driver, so changing
just this one like that does not make a lot of sense to me.
Maybe mmio regmap should '.use_raw_spinlock = true' by default when
'.fast_io' is set ?
Mark, what is your opinion on this ? I guess it is not the first time
this occurs ?
>
> [ ] =============================
> [ ] [ BUG: Invalid wait context ]
> [ ] 6.9.9-sdkernel #1 Tainted: G O
> [ ] -----------------------------
> [ ] aplay/413 is trying to lock:
> [ ] ffff000003930018 (axg_fifo:356:(&axg_fifo_regmap_cfg)->lock){....}-{3:3},c
> [ ] other info that might help us debug this:
> [ ] context-{2:2}
> [ ] no locks held by aplay/413.
> [ ] stack backtrace:
> [ ] CPU: 0 PID: 413 Comm: aplay Tainted: G O 6.9.9-kernel #1
> [ ] Hardware name: SberDevices SberBoom Mini (DT)
> [ ] Call trace:
> [ ] dump_backtrace+0x98/0xf0
> [ ] show_stack+0x18/0x24
> [ ] dump_stack_lvl+0x90/0xd0
> [ ] dump_stack+0x18/0x24
> [ ] __lock_acquire+0x9dc/0x1f10
> [ ] lock_acquire.part.0+0xe8/0x228
> [ ] lock_acquire+0x68/0x84
> [ ] _raw_spin_lock_irqsave+0x60/0x88
> [ ] regmap_lock_spinlock+0x18/0x2c
> [ ] regmap_read+0x3c/0x78
> [ ] axg_fifo_pcm_irq_block+0x4c/0xc8
> [ ] __handle_irq_event_percpu+0xa4/0x2f8
> [ ] handle_irq_event+0x4c/0xbc
> [ ] handle_fasteoi_irq+0xa4/0x23c
> [ ] generic_handle_domain_irq+0x2c/0x44
> [ ] gic_handle_irq+0x40/0xc4
> [ ] call_on_irq_stack+0x24/0x4c
> [ ] do_interrupt_handler+0x80/0x84
> [ ] el0_interrupt+0x5c/0x124
> [ ] __el0_irq_handler_common+0x18/0x24
> [ ] el0t_32_irq_handler+0x10/0x1c
> [ ] el0t_32_irq+0x194/0x198
>
> Signed-off-by: Arseniy Krasnov <avkrasnov@salutedevices.com>
> ---
> sound/soc/meson/axg-fifo.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sound/soc/meson/axg-fifo.c b/sound/soc/meson/axg-fifo.c
> index ecb3eb7a9723d..a22298f74b35a 100644
> --- a/sound/soc/meson/axg-fifo.c
> +++ b/sound/soc/meson/axg-fifo.c
> @@ -328,6 +328,7 @@ static const struct regmap_config axg_fifo_regmap_cfg = {
> .val_bits = 32,
> .reg_stride = 4,
> .max_register = FIFO_CTRL2,
> + .use_raw_spinlock = true,
> };
>
> int axg_fifo_probe(struct platform_device *pdev)
--
Jerome
next prev parent reply other threads:[~2024-07-29 14:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 13:16 [PATCH v1] ASoC: meson: axg-fifo: set option to use raw spinlock Arseniy Krasnov
2024-07-29 14:15 ` Jerome Brunet [this message]
2024-07-29 14:44 ` Mark Brown
2024-07-29 15:06 ` Jerome Brunet
2024-07-29 15:28 ` Mark Brown
2024-07-29 15:57 ` Jerome Brunet
2024-08-05 15:33 ` Sebastian Andrzej Siewior
2024-08-05 16:07 ` Jerome Brunet
2024-08-06 6:50 ` Sebastian Andrzej Siewior
2024-08-06 9:21 ` Jerome Brunet
2024-08-06 10:03 ` Sebastian Andrzej Siewior
2024-08-05 16:56 ` Mark Brown
2024-08-06 6:57 ` Sebastian Andrzej Siewior
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=1ja5i0wags.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=avkrasnov@salutedevices.com \
--cc=broonie@kernel.org \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=oxffffaa@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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