From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org,
Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: ep93xx: ignore 0 Hz sysclk
Date: Mon, 13 Feb 2023 16:18:43 +0000 [thread overview]
Message-ID: <167630512330.2770751.11991611476848663796.b4-ty@kernel.org> (raw)
In-Reply-To: <20230212220923.258414-1-alexander.sverdlin@gmail.com>
On Sun, 12 Feb 2023 23:09:23 +0100, Alexander Sverdlin wrote:
> Commit 2458adb8f92a
> ("SoC: simple-card-utils: set 0Hz to sysclk when shutdown")
> added a call to snd_soc_dai_set_sysclk() with 0 Hz frequency. Being
> propagated further it causes a division by zero in clk-ep93xx driver:
>
> Division by zero in kernel.
> CPU: 0 PID: 52 Comm: aplay Tainted: G W 6.2.0-rc4-... #1
> Hardware name: Generic DT based system
> unwind_backtrace from show_stack+0x10/0x18
> show_stack from dump_stack_lvl+0x28/0x34
> dump_stack_lvl from __div0+0x10/0x1c
> __div0 from Ldiv0+0x8/0x1c
> Ldiv0 from ep93xx_mux_determine_rate+0x78/0x1d0
> ep93xx_mux_determine_rate from clk_core_round_rate_nolock+0x48/0xc8
> clk_core_round_rate_nolock from clk_core_set_rate_nolock+0x48/0x160
> clk_core_set_rate_nolock from clk_set_rate+0x30/0x8c
> clk_set_rate from ep93xx_i2s_set_sysclk+0x30/0x6c
> ep93xx_i2s_set_sysclk from snd_soc_dai_set_sysclk+0x3c/0xa4
> snd_soc_dai_set_sysclk from asoc_simple_shutdown+0xb8/0x164
> asoc_simple_shutdown from snd_soc_link_shutdown+0x44/0x54
> snd_soc_link_shutdown from soc_pcm_clean+0x78/0x180
> soc_pcm_clean from soc_pcm_close+0x28/0x40
> soc_pcm_close from snd_pcm_release_substream.part.0+0x3c/0x84
> snd_pcm_release_substream.part.0 from snd_pcm_release+0x40/0x88
> snd_pcm_release from __fput+0x74/0x278
>
> [...]
Applied to
broonie/sound.git for-next
Thanks!
[1/1] ASoC: ep93xx: ignore 0 Hz sysclk
commit: 66dc3b9b9a6f4b5c7013f15c66073ddd20852b66
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2023-02-13 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 22:09 Alexander Sverdlin
2023-02-13 16:18 ` Mark Brown [this message]
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=167630512330.2770751.11991611476848663796.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexander.sverdlin@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®