x/exp/io: introduce pin mappings #15773
Labels
Milestone
Comments
|
Chatting more about this issue with @proppy offline, we are thinking that the virtual pin space doesn't have to be of string names but we can keep using ints to defer to the GPIO numbers. Yet, we still need to have a mechanism to map the virtual pin space to the physical pins (at least for the /dev/mem implementation). /cc @minux |
|
We could consider a register mechanism, and introduce board support
packages that registers pin names to the io/gpio package.
Because usually a pin will have multiple uses (btw, which package should
control the pin mux that selects the functionality of each pin?), if we're
going to use string for pin names, we will need to allow multiple aliases
for a single pin.
|
|
Closed via golang/exp@abad524. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Due to the fact that every board has different mappings of the actual physical pins, we need to introduce a higher level layer numeric system to name the pins. Being able to have such a layer will make the user code portable across multiple boards. E.g. the GPIO package might use names like "IO25" to refer to the physical pin 22 on Raspberry Pi boards.
The text was updated successfully, but these errors were encountered: