Chris Johns commented on a discussion on cpukit/include/dev/gpio/gpio.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1499#note_159739 > + * > + * What a pin reads as before rtems_gpio_pin_configure() is called on it, > + * and what it returns to after rtems_gpio_pin_release(). > + */ > + RTEMS_GPIO_DIRECTION_NONE = 0, > + > + /** > + * @brief This enumerator indicates that the pin is an input. > + */ > + RTEMS_GPIO_DIRECTION_INPUT, > + > + /** > + * @brief This enumerator indicates that the pin is an output. > + */ > + RTEMS_GPIO_DIRECTION_OUTPUT > +} rtems_gpio_direction; I do not understand what an `analog` setting means? The driver is responsible for only exporting pins from the device that can be used as GPIO. The GPIO number is logical and not physical. For example a Zynq's GPIO pins are defined by Vivado from the MIO pins. If only 5 pins are configured as GPIO only 5 pins are available and they are number 0-4. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1499#note_159739 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/5-c4piwrtbl2gys2xcbhrqse3yv-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
