-
Notifications
You must be signed in to change notification settings - Fork 323
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.
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
topology2: pipeline: document pipeline.priority attribute #8509
topology2: pipeline: document pipeline.priority attribute #8509
Conversation
@@ -57,7 +57,7 @@ Class.Widget."pipeline" { | |||
} | |||
} | |||
|
|||
# pipeline priority | |||
# pipeline priority (0 = highest priority) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add more? like priority range: 0 ~ ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, yeah, also useful to add "lowest = 7" iirc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@btian1 @lgirdwood I agree but this is complex. 0 = highest applies to all implementations, but fine details of other semantics are still a bit unclear to me, including what is the lowest. in IPC4 this is 7, but we don't have such for IPC3. but fair enough, let me investigate more to come up with the documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needed addition.
@@ -57,7 +57,7 @@ Class.Widget."pipeline" { | |||
} | |||
} | |||
|
|||
# pipeline priority | |||
# pipeline priority (0 = highest priority) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, yeah, also useful to add "lowest = 7" iirc.
Add constraints on valid pipeline priority values and document the semantics so that 0 is considered the highest priority and such pipeline should be run first. The range matches definitions in include/ipc4/pipeline.h and SOF_IPC4_MAX_PIPELINE_PRIORITY. Signed-off-by: Kai Vehmanen <[email protected]>
22f7dbe
to
179bbd5
Compare
V2:
|
SOFCI TEST |
Add a note that priority 0 is the highest priority and indicates pipeline that should be run first. This matches with the SOF scheduler implementation.