Re: [PATCH v2 0/9] ASoC: stop dependent resume work after restore failures

[Mark Brown]

On Wed, 14 Oct 2026 11:24:43 +0800, Pengpeng Hou wrote:
> ASoC: stop dependent resume work after restore failures
> 
> This revision addresses Mark's cache-mode concern and Charles's WM8978
> bias rollback question. It also accounts for the next suspend after a
> failed resume: the ASoC wrapper reports the callback error but marks the
> component resumed, so leaving an IRQ disabled needs driver-local ownership
> tracking to avoid disabling it a second time in the next suspend.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.5

Thanks!

[1/9] ASoC: nau8821: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/924b88cec6b5
[2/9] ASoC: nau8824: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/230d0320971f
[3/9] ASoC: nau8825: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/6bfb1abeee3b
[4/9] ASoC: rt5663: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/7cd349171991
[5/9] ASoC: rt5682s: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/9561e9be8996
[6/9] ASoC: rt5682: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/083dbbdfee9e
[7/9] ASoC: wm8978: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/947f7c8b9728
[8/9] ASoC: rt5640: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/de80fa166b95
[9/9] ASoC: rt5677: restore safe state after resume errors
      https://git.kernel.org/broonie/sound/c/d9dd3f68d6be

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