P4
A DESCRIPTION OF THE REQUEST :
Currently when using the Device IO library, there is a hard coded template that expects to use a gpio at /sys/class/gpio/gpio#, where # is passed in from opening the GPIO with DeviceManager. I am proposing that if the user specifies a name instead of a number, that the string be /sys/class/gpio/NAME instead when trying to manipulate the GPIO in linux.
JUSTIFICATION :
I have a platform that exposes gpios as strings like P3_1 for gpio 39, and P3_2 for gpio 40, etc. It doesn't use gpio39 and the name for gpio 39 when populating the device in /sys. It would be nice to not have to hack the kernel to use strings that the Java DIO is happy with - Java DIO should be a bit more flexible in allowing the user to specify the name of the gpio if it isn't standard.
CUSTOMER SUBMITTED WORKAROUND :
Fix the Linux kernel I am working on to expose GPIO names that Java DIO likes.
Currently when using the Device IO library, there is a hard coded template that expects to use a gpio at /sys/class/gpio/gpio#, where # is passed in from opening the GPIO with DeviceManager. I am proposing that if the user specifies a name instead of a number, that the string be /sys/class/gpio/NAME instead when trying to manipulate the GPIO in linux.
JUSTIFICATION :
I have a platform that exposes gpios as strings like P3_1 for gpio 39, and P3_2 for gpio 40, etc. It doesn't use gpio39 and the name for gpio 39 when populating the device in /sys. It would be nice to not have to hack the kernel to use strings that the Java DIO is happy with - Java DIO should be a bit more flexible in allowing the user to specify the name of the gpio if it isn't standard.
CUSTOMER SUBMITTED WORKAROUND :
Fix the Linux kernel I am working on to expose GPIO names that Java DIO likes.