audio: manage ISO transfer in ISR #3150
Open
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.
Describe the PR
2nd part of #3133, ISO transfer management is moved into USB ISR to avoid timing conflict with other classes.
Transfer callbacks become
tud_audio_tx_done_isr
/tud_audio_rx_done_isr
and not recommended to use, data should be read/write from audio process callback (I2S IRQ) instead.Meanwhile logging for ISR transfer is not easy to implement:
tusb_task()
is blocked by something since ISR transfer continuesTested on
NUCLEO-H7S3L8
andNUCLEO-C071RB
with all audio examples.Demo
audio_test_freertos
example, add some processing delay to volume change requestplot_audio_samples.py
script (increase recording duration if your hand is slow ;))