Implementation of GPIO access from Linux User Space. More...
Implementation of GPIO access from Linux User Space.
This module allows to connect a RIOT application that runs on a Linux host to the physical GPIO pins of that host. To do so, the application has to be compiled for the native board in a Linux environment.
GPIO support is automatically included if either a module requiring the
periph_gpio feature is added to the application or if it is explicitly listed as
FEATURES_REQUIRED in the application's Makefile.
At runtime, the process has to be connected to a specific GPIO bank on the host machine. GPIO banks are exposed as
/dev/gpiochipN character files, where N is the bank ID to which several GPIO pins are connected.
This will add
/dev/gpiochip1 as PORT(0) and PORT(1) in RIOT. The first pin can be used with PIN(0,0) as
gpio_t, the second one on the first port would be PIN(0,1) and so on.
Please refer to your board's documentation for the mapping of the pins.
|Implementation of GPIO access from Linux User Space. |
|int||gpio_linux_setup (const char *device)|
|shutdown GPIO subsystem More...|
|int gpio_linux_setup||(||const char *||device||)|
/dev/gpiochip* device to be used for GPIO
|[in]||device||The gpiochip device to open.|
shutdown GPIO subsystem
This closes all GPIO fds.