cpu/gd32v: fix gpio_read in periph_gpio #19418
Merged
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
gschorcht
added
Type: bug
|
@MrKevinWeiss This PR should be included in the Hard Freeze because it fixes a small but serious bug. |
benpicco
approved these changes
Mar 24, 2023
|
bors merge |
|
Build succeeded: |
# for free
to join this conversation on GitHub.
Already have an account?
# 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 a bug in
gpio_readwhich madegpio_readcompletely unusable!A small bug with big consequences. In
gpio_readthe combined port | pin_num parameterpinwas used instead of the pin numberpin_numfor the call of_pin_is_input. This caused the problem that for example instead of accessing GPIOA->CTL0 with address 0x40010800, address 0x60018c00 was accessed. As a result, a pin was randomly detected as input or output and thus a result was arbitrarily returned. Approx. 50% of all inputs always returned LOW.I found this error by coincidence when I tried to find out why the BOOT0 button on a Sipeed Longan Nano is not usable as a button in RIOT.
Testing procedure
Flash
tests/periph_gpioand use commands
Without this PR, the pin is always LOW. With the PR, the pin should be HIGH when the BOOT button is pressed.
Issues/PRs references