Re: [PATCH v2 0/9] ASoC: use sof_sdw as default Intel SOF SDW machine driver

[Mark Brown <broonie@kernel.org>]

On Tue, 14 Oct 2025 15:13:26 +0800, Bard Liao wrote:
> Currently, we create a ACPI mach table for every new audio
> configuration. And all Intel SOF SoundWire configurations point to the
> same sof_sdw machine driver. Also, we don't need a specific topology for
> a coufguration, we can use the function topology instead. That give us a
> change to generate an ACPI mach table based on the SoundWire codec
> information reported by the ACPI table and use the sof_sdw machine
> driver as the default machine driver.
> This will reduce the effort to support a new Intel SOF SoundWire audio
> configuration.
> 
> [...]

Applied to

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

Thanks!

[1/9] ASoC: SOF: Don't print the monolithic topology name if function topology may be used
      commit: 2b92b98cc4765fbb0748742e7e0dd94d15d6f178
[2/9] ASoC: soc-acpi: make some variables of acpi adr and link adr non-const
      commit: d25de16477657f9eddd4be9abd409515edcc3b9e
[3/9] ASoC: soc_sdw_utils: add name_prefix to asoc_sdw_codec_info struct
      commit: aa1ee85ce3576defd29f2a389d7508d2036af977
[4/9] ASoC: Intel: export sof_sdw_get_tplg_files
      commit: 7196fc4e482928a276da853e2687f31cd8ea2611
[5/9] ASoC: soc_sdw_utils: export asoc_sdw_get_dai_type
      commit: 5ed60e45c59d66e61586a10433e2b5527d4d72b5
[6/9] ASoC: SOF: add platform name into sof_intel_dsp_desc
      commit: 6937ff42f28a13ffdbe2d1f5b9a51a35f626e93a
[7/9] ASoC: SOF: don't check the existence of dummy topology
      commit: 99c159279c6dfa2c4867c7f76875f58263f8f43b
[8/9] ASoC: SOF: Intel: use sof_sdw as default SDW machine driver
      commit: 5226d19d4cae5398caeb93a6052bfb614e0099c7
[9/9] ASoC: sof-function-topology-lib: escalate the log when missing function topoplogy
      commit: 9797329220a2c6622411eb9ecf6a35b24ce09d04

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