manifest: optional: remove sof from optional manifest#97946
manifest: optional: remove sof from optional manifest#97946kartben merged 3 commits intozephyrproject-rtos:mainfrom
Conversation
|
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 1 removed project Note: This message is automatically posted and updated by the Manifest GitHub Action. |
7ec8d06 to
d691906
Compare
|
@LaurentiuM1234 see https://github.com/zephyrproject-rtos/zephyr/actions/runs/18662605621/job/53206439186?pr=97946. You are checking for CONFIG_SOF in various places, this is not correct and is basically a layering violation. SOF is not part of Zephyr and we should not depend on it for hardware configuration. Can can you please take a look and see how you can get this working with check for SOF? |
lgirdwood
left a comment
There was a problem hiding this comment.
Ack - SOF depends on Zephyr not a cyclic dependency.
|
@nashif wrote: I had no idea we had such a workaround. Any idea who added this comment? Git-blame gives me just the gigantic HWMv2 commit. It seems this is still depended on, builds will fail if I remove this. |
|
@kv2019i Is this something we can fix in SOF, ie. in with: diff --git a/src/arch/host/Kconfig b/src/arch/host/Kconfig
index de92f43a8..5ef3f7420 100644
--- a/src/arch/host/Kconfig
+++ b/src/arch/host/Kconfig
@@ -4,6 +4,6 @@
config CORE_COUNT
int
- default 1
+ default MP_MAX_NUM_CPUS
help
Number of used cores |
efe8831 to
9f338e3
Compare
|
see thesofproject/sof#10321 for changes needed on the SOF side |
9f338e3 to
44c214d
Compare
| labels: | ||
| - "area: Debugging" | ||
|
|
||
| "West project: sof": |
There was a problem hiding this comment.
typo in commit message: "Nothing in Zephyr uses SOF" was probably meant
Nothing in Zephyr uses SOF, it is the other way round, SOF uses Zephyr, creating a cyclic dependency in some cases making it difficult to apply changes to areas used by SOF upstream. Part of zephyrproject-rtos#91061 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
During transition to HWMv2 this workaround was added, which should instead be in SOF and not in Zephyr, as CORE_COUNT is a SOF Kconfig. Remove this and instead set the CORE_COUNT in SOF to the MP_MAX_NUM_CPUS. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Do not depend on SOF config, use RIMAGE_SCHEMA instead, defined in SOF. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
44c214d to
0424ca3
Compare
|
|
@nashif would be nice to add sof as an external module then? |



Nothing in Zephyr uses SOF, it is the other way round, SOF uses
Zephyr, creating a cyclic dependency in some cases making it difficult
to apply changes to areas used by SOF upstream.
Part of #91061
Signed-off-by: Anas Nashif anas.nashif@intel.com