The first 3 patches in this series add some more KUnit testing for
fetching speaker ID and combining it with the system name to create
part of the qualifier for a firmware filename.

Patch #4 enables GPIOLIB in KUnit 'alltests' builds. This can be taken
separately from the first 3 patches.

The GPIO tests will skip if GPIOLIB is not enabled, but obviously it
would be ideal for 'kunit.py --alltests' runs to include these new
test cases.

Richard Fitzgerald (4):
  ASoC: cs35l56: KUnit tests for setting dsp.system_name
  ASoC: cs35l56: Some KUnit testing of cs35l56_get_speaker_id()
  ASoC: cs35l56: KUnit tests for reading speaker ID from host GPIOs
  kunit: config: all_tests: Select CONFIG_GPIOLIB

 sound/soc/codecs/cs-amp-lib.c                |   2 +
 sound/soc/codecs/cs35l56-shared-test.c       | 240 +++++++++++++++++++
 sound/soc/codecs/cs35l56-test.c              |  80 +++++++
 sound/soc/codecs/cs35l56.c                   |   3 +-
 sound/soc/codecs/cs35l56.h                   |   1 +
 tools/testing/kunit/configs/all_tests.config |   2 +
 6 files changed, 327 insertions(+), 1 deletion(-)

-- 
2.47.3

On Wed, 04 Mar 2026 16:23:58 +0000, Richard Fitzgerald wrote:
> The first 3 patches in this series add some more KUnit testing for
> fetching speaker ID and combining it with the system name to create
> part of the qualifier for a firmware filename.
> 
> Patch #4 enables GPIOLIB in KUnit 'alltests' builds. This can be taken
> separately from the first 3 patches.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: cs35l56: KUnit tests for setting dsp.system_name
      commit: bae6668c526018af45b70e7825b61e6edb528f41
[2/4] ASoC: cs35l56: Some KUnit testing of cs35l56_get_speaker_id()
      commit: 72e1c4704844766c46725d6b043ba04559054d02
[3/4] ASoC: cs35l56: KUnit tests for reading speaker ID from host GPIOs
      commit: ef0b4783afc211a4b120e72b5a57f3d0340a9981

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