You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of the arbitrary nature of LED's pin selection, allowing for selecting any available number, the module needs to fetch the GPIO through the global number,
So the legacy GPIO interface was used to request/free, while the new interface was used to set the values.
(There may be other ways to do this, that was the fastest found).
Upon a pin change through userspace, the module is able to configure a new GPIO device/pin and free/release the previous one set.
It also allows to undefine the pin number (-1).
For testing purposes, the module initialized the GPIO as HIGH, allowing it to be visualized.
2 LEDs were attached to pins 65 and 66 and the module initialized with 1 LED. The LED's pin was then changed between 65, 66 and -1 and the respective LED was lighted.
The module, upon receiving a pin number change, should destroy the old configuration and initialize a new one, for the respective LED/GPIO.
DoD: module re-initializes new GPIO configuration after pin change
Blocker: #3
The text was updated successfully, but these errors were encountered: