ASoC: SOF: Intel: pci-mtl: Change the topology path to intel/sof-ipc4-tplg
Subsystems (3)
Peter Ujfalusi
maintainerPATCH 1/1 ASoC: SOF: Intel: pci-mtl: Change the topology path to intel/sof-ipc4-tplg
The default topology path for IPC4 is intel/sof-ipc4-tplg with a symlink to it as intel/sof-ace-tplg to support old kernels.
sof-bin has been released in this manner for almost two years now, it is time to change the default path for MTL family.
--- sound/soc/sof/intel/pci-mtl.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
sound/soc/sof/intel/pci-mtl.c +3 -3
@@ -47,7 +47,7 @@ static const struct sof_dev_desc mtl_desc = { [SOF_IPC_TYPE_4 ] ="intel/sof-ipc4-lib/mtl" , }, .default_tplg_path = { - [SOF_IPC_TYPE_4 ] ="intel/sof-ace-tplg" , + [SOF_IPC_TYPE_4 ] ="intel/sof-ipc4-tplg" , }, .default_fw_filename = { [SOF_IPC_TYPE_4 ] ="sof-mtl.ri" ,
@@ -77,7 +77,7 @@ static const struct sof_dev_desc arl_desc = { [SOF_IPC_TYPE_4 ] ="intel/sof-ipc4-lib/arl" , }, .default_tplg_path = { - [SOF_IPC_TYPE_4 ] ="intel/sof-ace-tplg" , + [SOF_IPC_TYPE_4 ] ="intel/sof-ipc4-tplg" , }, .default_fw_filename = { [SOF_IPC_TYPE_4 ] ="sof-arl.ri" ,
@@ -107,7 +107,7 @@ static const struct sof_dev_desc arl_s_desc = { [SOF_IPC_TYPE_4 ] ="intel/sof-ipc4-lib/arl-s" , }, .default_tplg_path = { - [SOF_IPC_TYPE_4 ] ="intel/sof-ace-tplg" , + [SOF_IPC_TYPE_4 ] ="intel/sof-ipc4-tplg" , }, .default_fw_filename = { [SOF_IPC_TYPE_4 ] ="sof-arl-s.ri" ,
Signature · 1 line
2.52.0
Mark Brown
maintainerQuoted 6 lines · Peter Ujfalusi
The default topology path for IPC4 is intel/sof-ipc4-tplg with a symlink to it as intel/sof-ace-tplg to support old kernels.
sof-bin has been released in this manner for almost two years now, it is time to change the default path for MTL family.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SOF: Intel: pci-mtl: Change the topology path to intel/sof-ipc4-tplg
commit: 544c0494cdb3732281e1f2e279cfa561724355db
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