Mark xcu status done in CU XGQ check #8697
Open
+2
−0
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.
Problem solved by the commit
Mark xcu status done in CU XGQ check.
This change is made to mark the done status of xcu xgq command to avoid calling down_timeout() on semaphore twice.
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
The entry in xgq completion list may not have been added by the time the cu interrupt thread polls and calls down_timout()
on semaphore. If the command done status is not set, the down_timeout() is called twice resulting in CU_TIMER timeout and causing unnecessary delay.
How problem was solved, alternative solutions (if any) and why they were rejected
Mark command status done so that the down_timeout() is called only once.
Risks (if any) associated the changes in the commit
None
What has been tested and how, request additional testing if necessary
Ran the filter2d application multiple times and verified the no CU_TIMER delay is encountered.
Documentation impact (if any)
None