Repository navigation
SPI NOR: the bits of SR3_DRV0 and SR3_DRV1 - #55
Merged
Merged
Conversation
DRV0 and DRV1 are bits 5 and 6 of status register 3, as the Registers view has them. Neither constant is used, the binary does not change.
PR Summary by QodoCorrect SPI NOR SR3 drive-strength bit masks
AI Description
High-Level Assessment
Files changed (1)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can commit Qodo's fix in one click with committable suggestions (GitHub & GitLab) |
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.
DRV0 and DRV1 are bits 5 and 6 of status register 3 (
0x20,0x40), as the Registers view of the web mode and the Android app has them; the constants said0x08and0x10.Neither constant is used: the native build has the same SHA-256 before and after, so this is
no-release, with no new version. Build and tests pass in the container.