ports/riot: change for structured GPIO type #3
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
force-pushed
the
riot_gpio_ext_api
branch
from
400e7d9
to
7ab9498
Compare
gschorcht
force-pushed
the
riot_gpio_ext_api
branch
from
7ab9498
to
7891f2d
Compare
OlegHahm
pushed a commit
to OlegHahm/micropython
that referenced
this pull request
Dec 6, 2023
Add SPI peripheral support
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.
During the migration process of the proposed GPIO API in RIOT-OS/RIOT#14602 we will need two different
printfcalls inmachine_pin_print. One using the scalargpio_tfor platforms that are using the legacy GPIO API and one for the structuredgpio_tfor platforms that already use the new extendable GPIO API.Both versions have been tested.