Skip to content

Conversation

@ujfalusi
Copy link
Collaborator

…-tplg

The firmware release which going to introduce support for Lunar Lake will use the documented default topology directory for IPC4: intel/sof-ipc4-tplg

Change the default path accordingly before sof-bin (sof-firmware) release includes Lunar Lake firmware and topologies.

Link: https://github.com/thesofproject/sof-docs/blob/master/getting_started/intel_debug/introduction.rst#2-topology-file

…-tplg

The firmware release which going to introduce support for Lunar Lake will
use the documented default topology directory for IPC4:
intel/sof-ipc4-tplg

Change the default path accordingly before sof-bin (sof-firmware) release
includes Lunar Lake firmware and topologies.

Link: https://github.com/thesofproject/sof-docs/blob/master/getting_started/intel_debug/introduction.rst#2-topology-file
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
},
.default_tplg_path = {
[SOF_IPC_TYPE_4] = "intel/sof-ace-tplg",
[SOF_IPC_TYPE_4] = "intel/sof-ipc4-tplg",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For IPC4 are there any specific modifications in topology? Or just the file location?

Will IPC4 work with topology1 files?

Thanks!

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IPC4 needs topology2 files. We want to keep these separate as we might have platforms (officially) supported by both IPC3 (topology1) and IPC4 (topology2) in upstream.

Copy link
Collaborator

@kv2019i kv2019i Jan 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iuliana-prodan @ujfalusi There's no strict dependency, you can write IPC3 tplgs with tplg1 or tplg2, and in reverse, you can write IPC4 tplgs with tplg1 or tplg2. That said, available common macro definitions to define pipelines limit the options so that currently you'll have to use tplg2 for IPC4 and tplg1 for IPC3.
UPDATE: so in short: "tplg1 == m4 preprocessing", "tplg2 == alsaconf preprocessing"

Copy link
Collaborator Author

@ujfalusi ujfalusi Jan 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kv2019i, thanks for the correction!
But the same topology file cannot be used by IPC3 and IPC4, right?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ujfalusi Ack, the kernel will expect different entities in the tplg file for IPC3 and IPC4, so a single tplg file cannot provide both,.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kv2019i is there any example of tplg1 file working with IPC4?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iuliana-prodan Unfortunately no, all the Intel work for IPC4 was done with the tplg2 frontend.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @kv2019i, @ujfalusi

Copy link
Member

@plbossart plbossart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval conditional on CI / daily tests passing.

@plbossart
Copy link
Member

@aiChaoSONG @ujfalusi please merge when all CI prerequisites are met.

@bardliao bardliao merged commit 0ba5acc into thesofproject:topic/sof-dev Jan 22, 2024
@ujfalusi ujfalusi deleted the peter/sof/pr/lnl_tplg_path_01 branch December 13, 2024 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants