Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/schedule/CMakeLists.txt
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ if (CONFIG_SOC_ACP_6_0)
)
else()
zephyr_library_sources(
ll_schedule.c
ll_schedule_xtos.c
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both "xtos" and "legacy" are fine to use, although "xtos" is more common here.

But I'm not sure if building the xtos version from the main branch is still possible? Even build scripts like xtensa-build-all.sh were removed.

Copy link
Member

@lgirdwood lgirdwood Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point @abonislawski , xtos version should no longer be buildable but IIRC there are some lingering headers that have to be removed before all xtos file can go completely.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@abonislawski @lgirdwood This is only used by AMD ACP6.0 build target (CONFIG_SOC_ACP_6_0), and when it's build without DMA scheduling. This is a Zephyr build, so not sure how this works, but SOF did provide migration tools to run XTOS code over Zephyr like this. I'm not sure if this is actively used, but the build target exists, so I don't want to remove the file.

I picked the "_xtos" prefix as then it's easier to note and remember to remember when we drop this target.

)
endif()
else()
Expand Down
File renamed without changes.
Loading