-
Notifications
You must be signed in to change notification settings - Fork 7.6k
drivers: gpio_rpi_pico: Extend the driver API #84548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
kartben
merged 5 commits into
zephyrproject-rtos:main
from
ajf58:rpi-pico-add-gpio-get-config-api
Feb 14, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
47bd3b8
drivers: gpio_rpi_pico: Support GPIO_DISCONNECTED flag
ajf58 a755082
drivers: gpio_rpi_pico: Disable inputs when not in use
ajf58 8e56bfc
drivers: gpio_rpi_pico: Add gpio_get_pending_int API
ajf58 5fb06d4
drivers: gpio_rpi_pico: Add gpio_port_get_direction API
ajf58 c39f6f3
drivers: gpio_rpi_pico: Add gpio_get_config API
ajf58 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that the RP2xxx series is documented as supporting reading from input pins at any time, does it make sense to disable the pad here? It seems to me that the pad should only be disabled if the application explicitly requests. (Of course, that leaves the question of should there be a Zephyr way to explicitly disable an input ...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a a good question. Zephyr's unit tests for
gpio_pin_get_config
require that pin config is explicit, i.e. ifgpio_pin_get_config
setGPIO_INPUT
on every pin, the test will fail.I think it is explicit already: if someone wants an output that's also an input, they should use
GPIO_INPUT | GPIO_OUTPUT
.