SGPIO deadline check #1510
Merged
SGPIO deadline check #1510
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
martinling
force-pushed
the
sgpio-deadline-check
branch
from
9689ed4 to
cdc3efa
Compare
Counter-intuitively, this actually saves us two cycles because we unroll the first iteration of the loop that spins on the interrupt flag, saving a branch in the case that the flag is clear the first time.
martinling
force-pushed
the
sgpio-deadline-check
branch
from
cdc3efa to
03551cb
Compare
mndza
approved these changes
Dec 3, 2024
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.
Checks whether the M0 core missed its deadline: i.e. if the next SGPIO interrupt already occurred by the time it finished processing the last one.
If so, the M0 returns to the idle mode with an error code in the M0 state. This should cause the host tools to time out, at which point the error can be checked with
hackrf_debug -S.