cpu/cortexm_common: flush pipeline before disabling interrupts in idle [backport 2020.10]#15238
Merged
bergzand merged 1 commit intoOct 17, 2020
Conversation
When enabling & disabling interrupts back-to-back pending interrupts are not serviced on Cortex-M23/M33. Flush the pipeline to give interrupts a chance of executing in `sched_arch_idle()`. This fixes `no_idle_thread` on Cortex-M23. (cherry picked from commit c48b331)
benpicco
requested review from
DipSwitch,
haukepetersen and
thomaseichinger
as code owners
benpicco
added
Area: cpu
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.
Backport of #15236
Contribution description
When enabling & disabling interrupts back-to-back pending interrupts are not serviced on Cortex-M23/M33.
Flush the pipeline to give interrupts a chance of executing in
sched_arch_idle().This fixes
no_idle_threadon Cortex-M23.Testing procedure
Issues/PRs references
#14557 (comment)