mbox series

[0/2] ASoC: SOF: Intel: pci-tgl/lnl: Change default paths for IPC4

Message ID 20240213080418.21256-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: Intel: pci-tgl/lnl: Change default paths for IPC4 | expand

Message

Peter Ujfalusi Feb. 13, 2024, 8:04 a.m. UTC
Hi,

Align the IPC4 firmware path/name and the topology path to the documentation:
default_fw_path:     intel/sof-ipc4/{platform_name}
default_lib_path:    intel/sof-ipc4-lib/{platform_name}
default_tplg_path:   intel/sof-ipc4-tplg
default_fw_filename: sof-{platform_name}.ri

Tiger Lake and Lunar Lake support is not yet available via the official
firmware release, the paths can be changed now to avoid misalignment in the
future.

Regards,
Peter
---
Peter Ujfalusi (2):
  ASoC: SOF: Intel: pci-tgl: Change the default paths and firmware names
  ASoC: SOF: Intel: pci-lnl: Change the topology path to
    intel/sof-ipc4-tplg

 sound/soc/sof/intel/pci-lnl.c |  2 +-
 sound/soc/sof/intel/pci-tgl.c | 64 +++++++++++++++++------------------
 2 files changed, 33 insertions(+), 33 deletions(-)

Comments

Mark Brown Feb. 13, 2024, 6:31 p.m. UTC | #1
On Tue, 13 Feb 2024 10:04:16 +0200, Peter Ujfalusi wrote:
> Align the IPC4 firmware path/name and the topology path to the documentation:
> default_fw_path:     intel/sof-ipc4/{platform_name}
> default_lib_path:    intel/sof-ipc4-lib/{platform_name}
> default_tplg_path:   intel/sof-ipc4-tplg
> default_fw_filename: sof-{platform_name}.ri
> 
> Tiger Lake and Lunar Lake support is not yet available via the official
> firmware release, the paths can be changed now to avoid misalignment in the
> future.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: Intel: pci-tgl: Change the default paths and firmware names
      commit: d463bcd7eb341b5b6e6d9263a3bce9f405c2af98
[2/2] ASoC: SOF: Intel: pci-lnl: Change the topology path to intel/sof-ipc4-tplg
      commit: b029482011bffd57319507c2bf4c5a7e06eca756

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