FIR-799/1238 Suppress assertion after USB PHY is stopped - #17
Merged
shogo-sugihara merged 1 commit intoMar 19, 2025
Conversation
finger563
approved these changes
Mar 17, 2025
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.
This PR solves the following problems in the FIR-799 / 1238 tasks:
If osal_queue_empty() is executed immediately after the USB PHY is stopped, it will enter the assert state in the osal_queue_empty() function (Then the Niji reboots), so this modification suppresses this.
https://linear.app/backbonelabs/issue/FIR-799/investigate-whether-sleep-or-apb-locks-can-be-released-for-usb-suspend
https://linear.app/backbonelabs/issue/FIR-1238/update-bsp-to-support-new-d-external-pull-up-iox-pin