Use lower-prio IRQ on Pico to decompress AAC/MP3#85
Merged
Conversation
Owner
Author
|
|
Fixes #84 On the Pico, when decoding AAC or MP3, it can spend a long time in an IRQ state, blocking other IRQs from processing. While we need to run asynchronously, we don't need to block other IRQs. When a DMA IRQ fires and calls us to generate the next frame, fire another low priority IRQ and return immediately. In the worst case we still run ahead of the app with just a little overhead. In the best case we don't block GPIO or USB interrupts.
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
1 participant
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.
Fixes #84
On the Pico, when decoding AAC or MP3, it can spend a long time in an IRQ state, blocking other IRQs from processing. While we need to run asynchronously, we don't need to block other IRQs.
When a DMA IRQ fires and calls us to generate the next frame, fire another low priority IRQ and return immediately. In the worst case we still run ahead of the app with just a little overhead. In the best case we don't block GPIO or USB interrupts.