Skip to content

subset of #10945 #10984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kv2019i merged 8 commits into from
Jul 13, 2026
Merged

subset of #10945 #10984

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
c859e78
Zephyr: add a missing header
lyakh Jul 13, 2026
7b8e7dd
module: (cosmetic) fix two comments
lyakh Jul 2, 2026
13af60a
schedule: userspace: DP also runs in userspace when possible
lyakh Jul 2, 2026
1e64869
schedule: limit schedule_free() to testing only
lyakh Jul 2, 2026
99237ce
init: add a check for userspace schedulers
lyakh Jul 2, 2026
c5a179c
schedule: ll: make ll_sch_is_current() always available
lyakh Jul 2, 2026
4f8d93a
schedule: dp: don't use privileged instructions
lyakh Jul 8, 2026
13dc8d0
schedule: dp: zero-initialise private data pointer
lyakh Jul 10, 2026
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/schedule.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ static inline bool scheduler_is_user(int type)
* to user-space and only keep Zephyr scheduler logic in
* kernel
*/
return type == SOF_SCHEDULE_LL_TIMER;
return type == SOF_SCHEDULE_LL_TIMER || type == SOF_SCHEDULE_DP;
Comment thread
lyakh marked this conversation as resolved.

@kv2019i kv2019i Jul 13, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Hmm, this is a static helper and only used in LL-specific logic, so not sure if this is correct. Arguably this could be clarified, but do you intend to use this later for new logic...?

@lyakh lyakh Jul 13, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@kv2019i yes, it's needed for the large set (at least its today's version). We can drop it here now, since the current "main" anyway doesn't work with DP modules if built with userspace LL. And this commit alone doesn't fix that. Would that be preferred?

}

int schedule_task_init(struct task *task,
Expand Down