Guennadi Liakhovetski

most comments apply to both host and DAI

interesting. Comparing CI results to #8804: not very clear. The MTL failure there https://sof-ci.01.org/sofpr/PR8804/build2377/devicetest/index.html is similar to this PR's https://sof-ci.01.org/sofpr/PR8823/build2511/devicetest/index.html but their TGL failure https://sof-ci.01.org/sofpr/PR8804/build2378/devicetest/index.html is gone in our https://sof-ci.01.org/sofpr/PR8823/build2512/devicetest/index.html

> @abonislawski @lyakh @juimonen anything else still todo ? cache API ? @lgirdwood yes, moving over to the Zephyr native `z_xtensa_cache_*()` API is one of the remaining items. `irq_local_*able()` is...

> This issue is only relevant with IPC3+zephyr+topology1. Not sure if this will ever be fixed though @ranj063 why is this irrelevant for IPC4? IPC4 doesn't provide a scheduling period?

> @ranj063 array-support merged in #7113 so rebase will be needed @kv2019i wouldn't this be dropped in favour of #6981 or do we need both stream types in nocodec?

> Btw, @kfrydryx I didn't see this linked anywhere yet but we do have this https://thesofproject.github.io/latest/architectures/firmware/sof-zephyr/mpp_layer/async_messaging.html . Probably should be as a link in the pull request description. I think...

> @plbossart, @lyakh please unblock the PR or list the technical issues that still need to be addressed before merge. As agreed, the improved AMS design can be implemented incrementally...

> But THAT means that you tend to run out of heap memory quickly, @andyross sorry, why? Are there memory leaks?

I actually wanted to have a "dump IPC" feature but for a completely different reason - to use a live system to record topology IPC messages to then create an...

@ranj063 @xiulipan @wenqingfu what if we do this as a debugfs file with a blocking read? I'm not a huge fan of polluting the kernel log with potentially many (dozens?...