Fix LPSPI word unpacking in receive operations #176
Merged
+127
−39
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
LPSPI receive operations are reversing byte and half-word elements when they place data in the caller's buffer. We can show this using the revised loopback tests on an older LPSPI driver. The unpacking routines need to consider the frame boundary and the bit order when they deconstruct the 32 bit LPSPI word.
teburd
approved these changes
Nov 18, 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.
LPSPI receive operations are reversing byte and half-word elements when they place data in the caller's buffer. We can show this using the revised loopback tests on an older LPSPI driver.
The unpacking routines need to consider the frame boundary and the bit order when they deconstruct the 32 bit LPSPI word.