This series fixes two problems found in the probing process that
can cause a deadlock (patch #1) or a hang (patch #2) during
component_probe() until the wait for init_completion times out.

Richard Fitzgerald (2):
  ASoC: cs35l56: Fix potential probe() deadlock
  ASoC: cs35l56: Use complete_all() to signal init_completion

 sound/soc/codecs/cs35l56-i2c.c |  4 +---
 sound/soc/codecs/cs35l56-spi.c |  4 +---
 sound/soc/codecs/cs35l56.c     | 17 ++++++++++++++++-
 3 files changed, 18 insertions(+), 7 deletions(-)

-- 
2.47.3

On Thu, 16 Jul 2026 14:20:43 +0100, Richard Fitzgerald wrote:
> ASoC: cs35l56: Fixes for deadlock/hang during component_probe()
> 
> This series fixes two problems found in the probing process that
> can cause a deadlock (patch #1) or a hang (patch #2) during
> component_probe() until the wait for init_completion times out.
> 
> Richard Fitzgerald (2):
>   ASoC: cs35l56: Fix potential probe() deadlock
>   ASoC: cs35l56: Use complete_all() to signal init_completion
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: cs35l56: Fix potential probe() deadlock
      https://git.kernel.org/broonie/sound/c/93c2a8ea2454
[2/2] ASoC: cs35l56: Use complete_all() to signal init_completion
      https://git.kernel.org/broonie/sound/c/e0bffb63a2ed

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