[PATCH 0/3] ASoC: cs35l56: Change firmware filenames for SoundWire

Richard Fitzgerald posted 3 patches 4 months ago
Documentation/sound/codecs/cs35l56.rst | 13 +++++
sound/soc/codecs/cs35l56-sdw.c         | 18 ++++---
sound/soc/codecs/cs35l56.c             | 72 ++++++++++++++++++++++----
sound/soc/codecs/cs35l56.h             |  3 ++
sound/soc/codecs/wm_adsp.c             | 27 ++++++----
sound/soc/codecs/wm_adsp.h             |  2 +
6 files changed, 109 insertions(+), 26 deletions(-)
[PATCH 0/3] ASoC: cs35l56: Change firmware filenames for SoundWire
Posted by Richard Fitzgerald 4 months ago
Change the firmware filename format on SoundWire systems to
directly tie it to the physical amp it applies to. This is mainly
to decouple it from the ALSA prefix strings to avoid complications
when the SoundWire machine driver starts creating dailinks based on
SDCA Disco info instead of hardcoded match tables. It also avoids
errors from having to rename firmware files from a hardware-address
to a ALSA-prefix naming for Linux publication. There are already
published firmware files for the L56 B0 silicon so that has a fallback
scheme for backward compatibility which has been separated into its
own patch on top of the main change.

We'd like to get this into 6.16 so that the L63 support starts "clean"
with this new naming and we don't have to support one kernel version
with L63 using the old naming. Unfortunately we didn't manage to get
these patches through internal review and testing before the merge
window opened.

Richard Fitzgerald (3):
  ASoC: cs35l56: Use SoundWire address as firmware name suffix for new
    silicon
  ASoC: cs35l56: Use SoundWire address as alternate firmware suffix on
    L56 B0
  ASoC: doc: cs35l56: Update to add new SoundWire firmware filename
    suffix

 Documentation/sound/codecs/cs35l56.rst | 13 +++++
 sound/soc/codecs/cs35l56-sdw.c         | 18 ++++---
 sound/soc/codecs/cs35l56.c             | 72 ++++++++++++++++++++++----
 sound/soc/codecs/cs35l56.h             |  3 ++
 sound/soc/codecs/wm_adsp.c             | 27 ++++++----
 sound/soc/codecs/wm_adsp.h             |  2 +
 6 files changed, 109 insertions(+), 26 deletions(-)

-- 
2.43.0
Re: [PATCH 0/3] ASoC: cs35l56: Change firmware filenames for SoundWire
Posted by Mark Brown 3 months, 4 weeks ago
On Thu, 12 Jun 2025 13:14:25 +0100, Richard Fitzgerald wrote:
> Change the firmware filename format on SoundWire systems to
> directly tie it to the physical amp it applies to. This is mainly
> to decouple it from the ALSA prefix strings to avoid complications
> when the SoundWire machine driver starts creating dailinks based on
> SDCA Disco info instead of hardcoded match tables. It also avoids
> errors from having to rename firmware files from a hardware-address
> to a ALSA-prefix naming for Linux publication. There are already
> published firmware files for the L56 B0 silicon so that has a fallback
> scheme for backward compatibility which has been separated into its
> own patch on top of the main change.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: cs35l56: Use SoundWire address as firmware name suffix for new silicon
      commit: d1fc7687959b0fbf335815a8d808e6076b969309
[2/3] ASoC: cs35l56: Use SoundWire address as alternate firmware suffix on L56 B0
      commit: e5d5b3aebdc8acf9f52d1369a7744a2ab9ca591c
[3/3] ASoC: doc: cs35l56: Update to add new SoundWire firmware filename suffix
      commit: fa8fae5f82e48db1a06ba570a2a3fdc087fc93c0

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