AP_HAL_QURT: Fix SPI transfer special case #28613
Merged
+6
−0
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
|
Change was flight tested successfully. |
… passed in even though it is a read transaction.
katzfey
force-pushed
the
pr-fix-qurt-spi-transfer
branch
from
b11c723
to
e053418
Compare
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.
Fix the SPI transfer special case where a send buffer is passed in even though it is a read transaction. This happens in the IMU
driver now that it has been optimized. The send buffer is the same as the read buffer even though it's just doing a read. This is
perfectly fine by SPI standards but needs special case handling in the Qurt SPI driver.