linux-kernel - Re: [PATCH v2] ASoC: cs35l56: Fix deadlock in ASP1 mixer register initialization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Thu, 08 Feb 2024 20:56:24 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH v2] ASoC: cs35l56: Fix deadlock in ASP1 mixer register
 initialization

On Thu, 08 Feb 2024 12:37:42 +0000, Richard Fitzgerald wrote:
> Rewrite the handling of ASP1 TX mixer mux initialization to prevent a
> deadlock during component_remove().
> 
> The firmware can overwrite the ASP1 TX mixer registers with
> system-specific settings. This is mainly for hardware that uses the
> ASP as a chip-to-chip link controlled by the firmware. Because of this
> the driver cannot know the starting state of the ASP1 mixer muxes until
> the firmware has been downloaded and rebooted.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Fix deadlock in ASP1 mixer register initialization
      commit: c14f09f010cc569ae7e2f6ef02374f6bfef9917e

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