cpu/esp32: fix CS handling in spi_transfer_bytes#12538
Merged
maribu merged 1 commit intoRIOT-OS:masterfrom Oct 22, 2019
Merged
Conversation
If `SPI_CS_UNDEF` is given as the `cs` parameter, CS pin must not be handled by the driver. Furthermore, if `cont` parameter is true, CS pin must not be disabled at the end of one transfer.
maribu
approved these changes
Oct 22, 2019
Member
maribu
left a comment
There was a problem hiding this comment.
ACK. I'm 100% sure that the code works as expected.
Contributor
Author
|
@maribu Thanks a lot. |
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
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.
Contribution description
This PR fixes the CS pin handling in
spi_transfer_bytes. IfSPI_CS_UNDEFis given as thecsparameter, CS pin MUST not be handled by the driver.Testing procedure
It's a very small change. Compilation should be enough as test.
The change was tested with a complex device driver that is using SPI:
Issues/PRs references
Problem was figured out in #12118 when testing with #12518.