Flavio Ceolin

What do you think about do it modular, we can have plugins to logging into a shm or to a pipe or wherever the user want, Is it a bad...

> @ceolin Can you take a look at this? The PM call is failing in O0. Yep, I can take a look. This is not part of Zephyr's PM logic...

Just for curiosity, can you check what is the access mode for this address ? Not familiar with this part of SoF code, but I think `glb_addr_attr` should give you...

> Unfortunately the cAVS/MTL platforms put registers in that low 512M block, so we can't use the region protection bits to deny access. That region is marked rw/uncached. Whether or...

I may be missing something, but only baytrail and apollolake have support for translation. ``` src/platform/apollolake/include/arch/xtensa/config/core-isa.h:580:#define XCHAL_HAVE_XLT_CACHEATTR 1 /* region prot. w/translation */ src/platform/baytrail/include/arch/xtensa/config/core-isa.h:478:#define XCHAL_HAVE_XLT_CACHEATTR 1 /* region prot. w/translation...

> that all sounds wonderful... But reading from those addresses does generate an exception, so the DSP "knows" that they are invalid? I looked at some of the registers and...

v2: - Include Zephyr's header where macros are defined. It ensures that Zephyr will not redefine SoF macros.

v3: - Changed to only define some macros when not building for Zephyr

v4: - `GET_BITS` is not going to be exported by Zephyr at moment.https://github.com/zephyrproject-rtos/zephyr/pull/48963#issuecomment-1217148881

> The long term direction for SOF on Zephyr platforms is that IP drivers will migrate to Zephyr i.e. the need for bit setting macros will be reduced. We will...