stm32: dma: support ringbuffers with format changes #4563
Conversation
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
This adds support for ringbuffers with different word sizes between the buffer and the peripheral, resulting in data conversion by the DMA engine. The DMA engine performs casts as described in the reference manual, which are what one expects (truncating if target too short, prepending 0s if target to long). To avoid accidental casts and maintain the original behaviour I created a new constructor `new_with_aligment`. I am up for any name suggestions, ST calls these operations data alignments.
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.
This adds support for ringbuffers with different word sizes between the buffer and the peripheral, resulting in data conversion by the DMA engine. The DMA engine performs casts as described in the reference manual, which are what one expects (truncating if target too short, prepending 0s if target to long).
To avoid accidental casts and maintain the original behaviour I created a new constructor
new_with_aligment. I am up for any name suggestions, ST calls these operations data alignments.