west.yml: update zephyr to e876dee6f2e

[tmleman]

Total of 1426 453 976 commits.

Changes include:
54545430e46 drivers: sai: Fix compile time error with clang
96d654bbc86 west.yml: Update hal_xtensa revision
cf7e2e63c17 soc: intel_adsp: rework host IPC using IPC service
d910306fd00 soc: intel_adsp: remove IDC dt default for CONFIG_INTEL_ADSP_IPC
0b3b6f30a3d ipm: remove the Intel Audio DSP CAVS host IPM driver
a4225b1ee8b pm: Add constraint lists and APIs
ae1f13149fc pm: Extend pm notifier to be able to report substate
823c519db22 subsys/llext: Fail if section name index is outside strings area
2bc84dc6d62 subsys/llext: Fail if symbol name index is outside strings area
3f6734034a7 subsys/llext: Fail if stated symbol size doesn't fit elf_sym_t
c6b6c62c21b arch: xtensa: (cosmetic) simplify function prototypes
5c5e17f0f37 kernel: dynamic: Optimize stack pool usage
8658ce5c9ef drivers: dma: dw: Add power management state check in get_status

[Copilot]

Pull Request Overview

Updates the Zephyr revision in the west.yml manifest file to incorporate 934 commits with improvements across multiple subsystems including power management, LLEXT security, kernel optimization, and driver enhancements.

• Updated Zephyr revision from 5bef4a9d6264761c10d739b345eb2f7ded719099 to 06daf0e29ee1d7cfd8242f45f2ad04f2fd2b03b9

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[kv2019i]

@tmleman @lrudyX Seems internal/quickbuild fails to a infra error (rsync failing), does not seem to be related to this PR.

[tmleman]

@kv2019i we have problem with TGL build:

16:10:00,766 INFO  - FAILED: modules/sof/CMakeFiles/modules_sof.dir/buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c.obj 
16:10:00,766 INFO  - ccache /root/xtensa/XtDevTools/install/tools/RG-2017.8-linux/XtensaTools/bin/xt-xcc -DCC_OPTIMIZE_FLAGS=\"\" -DKERNEL -DK_HEAP_MEM_POOL_SIZE=8192 -DXCC_TOOLS_VERSION=\"xcc\" -D__ZEPHYR__=1 -DRELATIVE_FILE=\"../sof/src/platform/intel/cavs/platform.c\" -I/buildagent/workspace/24733/build-tgl/zephyr/include/generated/zephyr -I/buildagent/workspace/24733/zephyr/include -I/buildagent/workspace/24733/build-tgl/zephyr/include/generated -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/common -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/common/include -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/cavs -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/cavs/include -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/cavs/include/cavs25 -I/buildagent/workspace/24733/zephyr/drivers -I/buildagent/workspace/24733/sof/zephyr/include -I/buildagent/workspace/24733/zephyr/kernel/include -I/buildagent/workspace/24733/zeph...
16:10:00,767 INFO  - /buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c:111: error: unknown field ‘state_exit’ specified in initializer
16:10:00,767 INFO  - /buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c:111: warning: missing braces around initializer
16:10:00,767 INFO  - /buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c:111: warning: (near initialization for ‘pm_state_notifier._node’)
16:10:00,768 INFO  - /buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c:111: warning: initialization from incompatible pointer type

[kv2019i]

Aa, right, also caught by the public Jenkins CI build: https://sof-ci.01.org/sofpr/PR10268/build16186/build/firmware_community/tgl.log

[lgirdwood]

@kv2019i we have problem with TGL build:

16:10:00,766 INFO  - FAILED: modules/sof/CMakeFiles/modules_sof.dir/buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c.obj 
16:10:00,766 INFO  - ccache /root/xtensa/XtDevTools/install/tools/RG-2017.8-linux/XtensaTools/bin/xt-xcc -DCC_OPTIMIZE_FLAGS=\"\" -DKERNEL -DK_HEAP_MEM_POOL_SIZE=8192 -DXCC_TOOLS_VERSION=\"xcc\" -D__ZEPHYR__=1 -DRELATIVE_FILE=\"../sof/src/platform/intel/cavs/platform.c\" -I/buildagent/workspace/24733/build-tgl/zephyr/include/generated/zephyr -I/buildagent/workspace/24733/zephyr/include -I/buildagent/workspace/24733/build-tgl/zephyr/include/generated -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/common -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/common/include -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/cavs -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/cavs/include -I/buildagent/workspace/24733/zephyr/soc/intel/intel_adsp/cavs/include/cavs25 -I/buildagent/workspace/24733/zephyr/drivers -I/buildagent/workspace/24733/sof/zephyr/include -I/buildagent/workspace/24733/zephyr/kernel/include -I/buildagent/workspace/24733/zeph...
16:10:00,767 INFO  - /buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c:111: error: unknown field ‘state_exit’ specified in initializer
16:10:00,767 INFO  - /buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c:111: warning: missing braces around initializer
16:10:00,767 INFO  - /buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c:111: warning: (near initialization for ‘pm_state_notifier._node’)
16:10:00,768 INFO  - /buildagent/workspace/24733/sof/src/platform/intel/cavs/platform.c:111: warning: initialization from incompatible pointer type

@tmleman looks localized to that platform, can you prepend the build fix to this PR. Thanks !

[softwarecki]

The newer Zephyr version includes important fixes for llext.

[dbaluta]

@tmleman @softwarecki Would you considering updating the west.yml zephyr hash to also include this change:

commit 54545430e467abee5d1442a330c2729a3a3dde98
Author: Daniel Baluta <daniel.baluta@nxp.com>
Date:   Wed Oct 1 18:29:18 2025 +0300

    drivers: sai: Fix compile time error with clang

Or we should merge it as it is and I'll send a seperate update later?

[tmleman]

@dbaluta I updated the manifest to include the specified fix.

[dbaluta]

@tmleman thanks!

[tmleman]

Update, I placed the wrong hash in the manifest.

[kv2019i]

Now at least the xt-xcc build goes through, but something wrong still with Intel Internal CI...

[dbaluta]

Now at least the xt-xcc build goes through, but something wrong still with Intel Internal CI...

@kv2019i did your xt-xcc build failed too due to Zephyr commit? Is there a problem with CI infra or with failing tests?

commit 524b72ce4053018dbe65210315a0c4fae95d8b8b
Author: Rubin Gerritsen <rubin.gerritsen@nordicsemi.no>
Date:   Mon Aug 11 20:41:01 2025 +0200

    toolchain: llvm: Provide working BUILD_ASSERT macro

@lgirdwood we should update Zephyr hash weekly to avoid situations were we pull thousands of zephyr commits.

[tmleman]

@lgirdwood @dbaluta I had to reduce the scope of the update. A regression appeared, possibly even two:

• on MTL, we have a problem with loading LLEXT (AEC).
• on LNL and PTL, there are issues with power flows.

[dbaluta]

@tmleman so is this working? Can you bisect the faulty commit?

[lgirdwood]

@lgirdwood we should update Zephyr hash weekly to avoid situations were we pull thousands of zephyr commits.

Good question, I think this just means a smaller bisect, but still needs the effort to debug. It could be easiest to add more ztests upstream into Zephyr per platform to help reduce issues (obviously wont catch PM/IP issues but may catch llext and other generic features).

[tmleman]

@kv2019i I updated the manifest to the last working version. So far, only the issue with AEC has been resolved. The test has been removed from CI, and the fix is under review (#10309).

@dbaluta unfortunately, I can't update to the version with the fix you're interested in yet.

I want this PR to be merged, and then I'll make another update after resolving the remaining issues.

[dbaluta]

@tmleman no worries. For our current release we create the imx-stable branch and we can handle it there.

Hopefully main can be fixed in the couple of next weeks when we restart testing it.