Fix device suspend issue introduced in interval timeout implementation#41
Merged
Conversation
Signed-off-by: chehan <chehan@qti.qualcomm.com>
hangzqcom
approved these changes
May 19, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
During D0 exit, cancelled URBs fire COMPLETION_EVENT with 0 bytes.
Without this status check, the timer would be re-armed while the device
is in Dx, causing the TimeoutReadQueue request to complete and apps
to post a new ReadFile into the power-managed ReadQueue, which
immediately wakes the device. This creates an infinite wake/sleep cycle
that prevents selective suspend.
Related Pull Request
Validation