RTEMS | dev/gpio: A generic GPIO API as a device node and ioctl (!1499)

[Sam Price (@TheSamPrice)]

Sam Price commented on a discussion on cpukit/include/dev/gpio/gpio.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1499#note_159843

 > +   *
 > +   * 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;

lm3s69xx is one of the bsps with a lot of those features being discussed 
## lm3s69xx 
- https://gitlab.rtems.org/rtems/rtos/rtems/-/blob/main/bsps/arm/lm3s69xx/include/bsp/io.h?ref_type=heads#L32
- https://gitlab.rtems.org/rtems/rtos/rtems/-/blob/main/bsps/arm/lm3s69xx/start/io.c?ref_type=heads

I did a summary of the GPIO features different BSPS are using 
https://users.rtems.org/t/rfc-gpio-api-as-a-driver-node-and-ioctl/936/2

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1499#note_159843
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-d8corlvhn7s1wvui31whj0u6u-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260923/d0d481c5/attachment-0001.htm>