[DNM / TEST] ipc4: idc: Print error message if trigger delay is ignored #8153
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Are we ignoring the delayed trigger on a remote core? Is it happening? Print out an error if it does. Signed-off-by: Peter Ujfalusi <[email protected]>
lgirdwood
reviewed
Sep 8, 2023
| ret = ipc4_pipeline_trigger(ppl_icd, cmd, &delayed); | ||
| if (delayed) | ||
| tr_err(&idc_tr, | ||
| "[NOT_RIGHT] idc: comp %d: cmd %d is delayed!!", |
There was a problem hiding this comment.
It has not trigger ed in the first test plan run, I will trigger a new one to see if it ever happens.
In theory the likeliness of this check to trigger should be the same as we have delayed trigger in the primary core.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Are we ignoring the delayed trigger on a remote core? Is it happening?
Print out an error if it does.