[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174558449287.45647.11999550141673145450.b4-ty@kernel.org>
Date: Fri, 25 Apr 2025 13:34:52 +0100
From: Mark Brown <broonie@...nel.org>
To: biju.das.jz@...renesas.com, prabhakar.mahadev-lad.rj@...renesas.com,
lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
Claudiu <claudiu.beznea@...on.dev>
Cc: linux-sound@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@...renesas.com>, stable@...r.kernel.org
Subject: Re: [PATCH] ASoC: renesas: rz-ssi: Use NOIRQ_SYSTEM_SLEEP_PM_OPS()
On Thu, 10 Apr 2025 17:15:25 +0300, Claudiu wrote:
> In the latest kernel versions system crashes were noticed occasionally
> during suspend/resume. This occurs because the RZ SSI suspend trigger
> (called from snd_soc_suspend()) is executed after rz_ssi_pm_ops->suspend()
> and it accesses IP registers. After the rz_ssi_pm_ops->suspend() is
> executed the IP clocks are disabled and its reset line is asserted.
>
> Since snd_soc_suspend() is invoked through snd_soc_pm_ops->suspend(),
> snd_soc_pm_ops is associated with soc_driver (defined in
> sound/soc/soc-core.c), and there is no parent-child relationship between
> soc_driver and rz_ssi_driver the power management subsystem does not
> enforce a specific suspend/resume order between the RZ SSI platform driver
> and soc_driver.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: renesas: rz-ssi: Use NOIRQ_SYSTEM_SLEEP_PM_OPS()
commit: c1b0f5183a4488b6b7790f834ce3a786725b3583
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
Powered by blists - more mailing lists