Some new Dell models use spare pins on the amp as a binary integer
value to indicate the speaker type. The driver must use this to
select the correct firmware files for the hardware.

Patch #1 is the new support.
The other patches are for KUnit testing.

Richard Fitzgerald (3):
  ASoC: cs35l56: Support for reading speaker ID from on-chip GPIOs
  ASoC: cs35l56-shared: KUnit tests for onchip speaker ID gpios
  ASoC: cs35l56: KUnit tests for parsing and using onchip GPIOs

 include/sound/cs35l56.h                |  37 ++
 sound/soc/codecs/Kconfig               |  14 +
 sound/soc/codecs/Makefile              |   2 +
 sound/soc/codecs/cs35l56-shared-test.c | 680 +++++++++++++++++++++++++
 sound/soc/codecs/cs35l56-shared.c      | 172 +++++++
 sound/soc/codecs/cs35l56-test.c        | 273 ++++++++++
 sound/soc/codecs/cs35l56.c             | 141 ++++-
 sound/soc/codecs/cs35l56.h             |   2 +
 8 files changed, 1317 insertions(+), 4 deletions(-)
 create mode 100644 sound/soc/codecs/cs35l56-shared-test.c

-- 
2.47.3

On Thu, 05 Feb 2026 16:48:35 +0000, Richard Fitzgerald wrote:
> Some new Dell models use spare pins on the amp as a binary integer
> value to indicate the speaker type. The driver must use this to
> select the correct firmware files for the hardware.
> 
> Patch #1 is the new support.
> The other patches are for KUnit testing.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: cs35l56: Support for reading speaker ID from on-chip GPIOs
      commit: 4d1e3e2c404dc30e039d81ba7396c8bb82ade991
[2/3] ASoC: cs35l56-shared: KUnit tests for onchip speaker ID gpios
      commit: 9bca0f05cea49ad11b464672ccdf6efd6a814a45
[3/3] ASoC: cs35l56: KUnit tests for parsing and using onchip GPIOs
      commit: 6f220440399afba29165e0597fa2c3aa836191d7

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