west.yml: update Zephyr to 5554fd17b651

[kv2019i]

Includes following commits affecting SOF targets:

3fde2c50c6ef tracing: add intel ADSP memory window backend
6b9d01f995c7 intel_adsp/ace: power: No pending transaction before power gate
64ba1b221091 dts: nxp: imx93: add nodes for SAI3 and EDMA4

[kv2019i]

@dbaluta @LaurentiuM1234 This seems to need a SOF side fix for
devicetree error: Label 'sai3' appears on /dai@42660000 and on /memory@42660000

@lyakh Really don't know what to do with the sparse checks? It's not really sustainable for SOF to check for things not done in Zephyr. Can we limit these checks to SOF code?

[LaurentiuM1234]

@dbaluta @LaurentiuM1234 This seems to need a SOF side fix for devicetree error: Label 'sai3' appears on /dai@42660000 and on /memory@42660000

@lyakh Really don't know what to do with the sparse checks? It's not really sustainable for SOF to check for things not done in Zephyr. Can we limit these checks to SOF code?

Thanks for the ping! Issue should be solved by #8520 which does the transition to Zephyr native drivers on 93. Is there any way we can merge that one first? (also does a Zephyr hash bump)

[lyakh]

@lyakh Really don't know what to do with the sparse checks? It's not really sustainable for SOF to check for things not done in Zephyr. Can we limit these checks to SOF code?

@kv2019i well, remember - it's Zephyr where sparse is actually called from, so, it would seem strange to me to have Zephyr call sparse while not letting it process Zephyr code itself

[kv2019i]

zephyrproject-rtos/zephyr#70725 filed for the mtl sparse zephyr warning.

[kv2019i]

#8945 merged instead, closing this one.