sam0/spi: fix SPI mode assignment#9885
Merged
PeterKietzmann merged 1 commit intoRIOT-OS:masterfrom Sep 10, 2018
Merged
Conversation
Signed-off-by: dylad <[email protected]>
Member
Author
|
@miri64 Any idea why Murdock complains here ? this is outside the scope of this PR right ? |
Member
Author
|
I retrigger Murdock and the previous error vanish... |
Member
|
@leandrolanzieri the code change seems reasonable. Can you confirm that it fixes #9695? |
Contributor
|
@PeterKietzmann yes, I scoped the signals and everything is looking good. |
Member
|
Great, thanks! |
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 provides a fix for #9695
The SPI mode selection is done using two bits in the SERCOM CTRLA register, bit 28 and bit 29.
The mode variable can be 0, 1, 2 or 3 but this variable was shifted to bit 29 instead of bit 28 (CPOL instead of CPHA) so the SPI mode was not set correctly.
More info in #9695
Thanks @leandrolanzieri for spotting this issue.
Testing procedure
Issues/PRs references