Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
There's no explicit check for the mux / demux type here. We just implicitly use the fact, that in case of a demux we would be coming into reset from the upstream source direction, so the single source is guaranteed to already be inactive? So the below condition
if (state > COMP_STATE_READY)can only trigger for a mux?Uh oh!
There was an error while loading. Please reload this page.
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.
AFAIK reset trigger starts from PCM and propagates downstream/upstream for playback/capture. It implies that for DEMUX on playback, reset can be received only when its (single) source got reset. Same concept for MUX on capture.
However I'm not sure if the trigger/propagation rule will be changed in the future. For example of MUX on capture, would it be possible to reset a PCM-less pipeline which presents as a branch of MUX upstream in multiple endpoints scheme? (like PPL#3 in the following graph)