Kai Vehmanen

I'd say an IPC to on-demand ask this information from FW would be the most suitable solution. So we could e.g. have a debugfs interface (exposed by SOF linux driver)...

V3 update: - major clean up, this should be now ready for @lgirdwood 's criteria of a minimal working set - keeping still as draft as the Zephyr PR needs...

V4 update: - implemented the worker thread using native interfaces -- a bit more code, but this is more efficient as we don't need to run anything extra in the...

V5 update: - improved the SOF EDF adaptation to Zephyr a bit and implemented the mtrace work thread logic using edf_schedule.h (this is basicly a k_thread pinned on a thread......

V6 update: - not included a manifest update to bring in the Zephyr dependencies - a few bugfixes to the EDF adaptation for recurring EDF tasks - added a more...

Zephyr builds errors are due to old SDK used in CI. 0.15 SDK is needed to build (or XCC).

V7 update: - updated github workflows to use a specific zephyr docker-image that containts 0.15 SDK - there is one IPC4 build failure left but that is a compiler warning...

V8 update: - fix XTOS IPC4 build caught by CI job "[checktree (IPC_VERSION=IPC4 UNSIGNED_list= SIGNED_list='tgl tgl-h cnl icl jsl')](https://github.com/thesofproject/sof/runs/8078564819?check_suite_focus=true#logs)"

V9 update: - addressed @abonislawski 's revies and most notably reviewed mtrace.[ch] to logging.[ch] as the same IPC can be used for other logging backends - one bugfix to disabling...

Hmm, this is an interesting config. Both the GPUs seem to be enabled, Intel and the Nvidia one. This may create issues as SOF driver does not support the vga-switcheroo...