Skip to content

Revert "ipc4: handler: maintain IPC set_pipeline_state order" #10868

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

Draft
serhiy-katsyuba-intel wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Revert "ipc4: handler: maintain IPC set_pipeline_state order" #10868

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c4f093b
ipc4: harden IPC4 pipeline triggering logic
serhiy-katsyuba-intel Jun 10, 2026
c291489
ipc4: assert IPC4 pipeline triggering logic
serhiy-katsyuba-intel Jun 10, 2026
e4ccefa
Revert "ipc4: handler: maintain IPC set_pipeline_state order"
serhiy-katsyuba-intel Jun 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
10 changes: 10 additions & 0 deletions src/audio/pipeline/pipeline-schedule.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -284,6 +284,16 @@ void pipeline_schedule_triggered(struct pipeline_walk_context *ctx,
struct pipeline *p;
uint32_t flags;

#ifdef CONFIG_IPC_MAJOR_4
/*
* With IPC4, each pipeline is triggered separately. Exactly 1 pipeline
* is expected in the pipelines list (it's unclear whether an empty list
* should be tolerated).
*/
assert(list_is_empty(&ctx->pipelines) ||

@lyakh lyakh Jun 12, 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.

@serhiy-katsyuba-intel have you ever seen empty lists here?

@serhiy-katsyuba-intel serhiy-katsyuba-intel Jun 12, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No, but the function will work without errors if an empty list is passed as a parameter. So I decided to add this check just to avoid introducing a crash when accessing the first list element without checking whether it exists.

list_item_is_last(ctx->pipelines.next, &ctx->pipelines));
#endif

/*
* Interrupts have to be disabled while adding tasks to or removing them
* from the scheduler list. Without that scheduling can begin
Expand Down