linux-kernel - Re: [PATCH v2 0/3] ASoC: cs35l56: Fixes for CS35L63 for production silicon

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]

Message-Id: <175572826017.300376.15142884398551755377.b4-ty@kernel.org>
Date: Wed, 20 Aug 2025 23:17:40 +0100
From: Mark Brown <broonie@...nel.org>
To: Stefan Binding <sbinding@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH v2 0/3] ASoC: cs35l56: Fixes for CS35L63 for production
 silicon

On Wed, 20 Aug 2025 13:50:33 +0100, Stefan Binding wrote:
> Production silicon for CS36L63 has some small differences compared to
> pre-production silicon. This requires small fixes in driver.
> Update firmware addresses, tuning algorithm IDs and remove soundwire
> clock workaround as no longer necessary.
> 
> No product was ever released using pre-production silicon, therefore
> there is no need to keep support for it.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: cs35l56: Update Firmware Addresses for CS35L63 for production silicon
      commit: f135fb24ef29335b94921077588cae445bc7f099
[2/3] ASoC: cs35l56: Handle new algorithms IDs for CS35L63
      commit: 8dadc11b67d4b83deff45e4889b3b5540b9c0a7f
[3/3] ASoC: cs35l56: Remove SoundWire Clock Divider workaround for CS35L63
      commit: 8d13d1bdb59d0a2c526869ee571ec51a3a887463

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