linux-kernel - Re: [PATCH v1 0/5] Add support for CS35L63 Smart Amplifier

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: <174661637867.4174662.14582168796180489522.b4-ty@kernel.org>
Date: Wed, 07 May 2025 20:12:58 +0900
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 v1 0/5] Add support for CS35L63 Smart Amplifier

On Mon, 07 Apr 2025 16:16:39 +0100, Stefan Binding wrote:
> CS35L63 is a Mono Class-D PC Smart Amplifier, with Speaker Protection
> and Audio Enhancement Algorithms.
> 
> CS35L63 uses a similar control interface to CS35L56 so support for
> it can be added into the CS35L56 driver.
> CS35L63 only has SoundWire and I2C control interfaces.
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: cs35l56: Add Index based on ACPI HID or SDW ID to select regmap config
      commit: 9ea280f3df60df014527ba5723fd8d1fd7c3b3ca
[2/5] ASoC: cs35l56: Add struct to index firmware registers
      commit: 8c0821ccaa1e53c30f6a51d034171e20d522a9c0
[3/5] ASoC: cs35l56: Add Mute, Volume and Posture registers to firmware register list
      commit: a3ec669efcee2cffd8ca020df777adbf79ac0b75
[4/5] ASoC: cs35l56: Add initial support for CS35L63 for I2C and SoundWire
      commit: 978858791cedaf1dbbbaeb1e37126611b7c28a9e
[5/5] ASoC: cs35l56: Read Silicon ID from DIE_STS registers for CS35L63
      commit: 406fbc4d0fb34c16718551bb8f4c776710f63b55

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