ober 28, 2021 7:28 PM
To: dev@nuttx.apache.org
Subject: [EXT] Re: ioexpander/gpio driver device names
Caution: EXT Email
Hi Jari and Alan,
I have a proof of concept of how a "more generic" way of using GPIOs could
work, actually running on my port of .NET nanoFramework for NuttX.
The ide
uttx.apache.org
Subject: [EXT] Re: ioexpander/gpio driver device names
Caution: EXT Email
Hi Jari and Alan,
I have a proof of concept of how a "more generic" way of using GPIOs could
work, actually running on my port of .NET nanoFramework for NuttX.
The idea is to have an entry per GPIO bank
Hi Jari and Alan,
I have a proof of concept of how a "more generic" way of using GPIOs
could work, actually running on my port of .NET nanoFramework for NuttX.
The idea is to have an entry per GPIO bank at `/dev/gpio{bank}`, so all
the pins of the bank would be managed by this entry.
NuttX s
Hi Jari,
I agree! Also in the Linux its name is just gpioN inside /sys.
But this modification will involve many boards modifications and also
the error message will need to give more details explaining that the
user cannot use that pin as input because it is configured to output
and vice-versa. A
Hi all,
I am currently working with the ioexpander/gpio driver to control GPIO pins
from an application. I am wondering if anybody is using this interface for more
practical applications than toggling a pin from the command line (i.e.
apps/examples/gpio).
I would say the interface is simple but
