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
Currently it is only possible to specify GPIO's as outputs see here.
I am proposing to add a DigitalInputProtocol together with a GpioDigitalInputDriver that configures GPIO pins as input only through sysfs (or switch to the newer devfs/libgpiod based GPIO interface while at it, because the sysfs one is deprecated).
This could ensure that there won't be any shorts when the pin is connected to an output of the DUT.
The text was updated successfully, but these errors were encountered:
Adding a corresponding DigitalInputProtocol and GpioDigitalInputDriver to the existing sysfs variant would be useful though. Sharing most of the agent code seems relatively easy. Do you intend to create a PR?
I see. Having to keep a process open is a limitation of the devfs based interface that I didn't have in mind. Yes, I intend to add it. I'll see if I can come up with a sysfs based implementation similar to the existing agent code then
Currently it is only possible to specify GPIO's as outputs see here.
I am proposing to add a
DigitalInputProtocol
together with aGpioDigitalInputDriver
that configures GPIO pins as input only through sysfs (or switch to the newer devfs/libgpiod based GPIO interface while at it, because the sysfs one is deprecated).This could ensure that there won't be any shorts when the pin is connected to an output of the DUT.
The text was updated successfully, but these errors were encountered: