configs: add ipc4 override config for tgl

[aiChaoSONG]

The override config can be used to build tgl
and tgl-h firmware with IPC4 configuration.

Signed-off-by: Chao Song [email protected]

[marc-hb]

There is already a generic -o option, can we use it instead? We should stop duplicating Kconfig into a shell script, it's messy and does not scale. See how the kernel does it: https://github.com/thesofproject/kconfig

Then we have to duplicate these options in yet another CI interface layer on top. Instead we need the ability to input any kconfig configuration to CI or anything: completely flexible and generic with no options duplicated in multiple layers to maintain.

EDIT:

• ASoC: SOF: add file names and paths for IPCv4 support linux#3382

[RanderWang]

LGTM

[lgirdwood]

Whats the use case ? I assume its to build for CI tests as this should also enable Zephyr.

[aiChaoSONG]

@lgirdwood It is used to build tigerlake firmware with IPC4 for CI and developers. sof+zephyr+ipc4 has build failure now, once it is fixed, it will be added in CI, too.

[lgirdwood]

@kkarask @wszypelt @mwasko - we can use the config for CI IPC4 mode.

[plbossart]

@aiChaoSONG @lgirdwood we need to have a different file name for the result, e.g. sof-tgl.ri4 or sof-tgl.bin4. this needs to be different from sof-tgl.ri, which will lead to confusions and support issues.

[lgirdwood]

@marc-hb are you able to update the appropriate CMakefile to use the ri4 file extension for IPC4 binaries (and topologies later) as I think @aiChaoSONG is off now for CNY

[marc-hb]

If this is top priority then yes I can. Thanks @ranj063 for @plbossart for providing some context. I need more, let's have a chat.

[marc-hb]

I expressed consistency concerns with .ri4: it would break *.ri scripts when the exact same rimage tool(s) are still used.

The current proposal seems to be sof-tgl-ipc4.ri

A (slightly) better place where this is being discussed too: thesofproject/sof-test#841

[marc-hb]

There is already a generic -o option, can we use it instead? We should stop duplicating Kconfig into a shell script, it's messy and does not scale.

I was wrong, apologies. Now that I know more about IPC4, I realize it's nothing like the usual Kconfig and deserves "top-level" interfaces. I will work on that.