Change interface to GPIO access to allow configuration of exported name

[Rob Cordeau]

Hi Alex,
I tried that and it's a no go in the sys directory. So I can either change
kernel source or change DIO source. I was hoping to upstream a change in
DIO source to increase its flexibility.

On Thursday, May 19, 2016, Alexander Mironenko <
alexander.mironenko at oracle.com> wrote:

> Hi Rob,
>
> Not sure, but may be you can create a symbolic link on each GPIO export?
> For instance you will have a link /sys/class/gpio/GPIO39 ->
> /sys/class/gpio/P3_1 and Java will work with it…
>
> It is just guess.
>
> Regards,
> Alex
>
> > On May 19, 2016, at 1:11 AM, Rob Cordeau <rscordeau at gmail.com
> <javascript:;>> wrote:
> >
> > Hi,
> > I am working on a board that exports GPIOs in a format that is different
> > than what dio expects.  Currently it is hard coded in dio to access a
> gpio
> > at /sys/class/gpio/gpio# when the gpio is exported, but the board I am on
> > has it configured in the kernel to export, say, GPIO39 as
> > /sys/class/gpio/P3_1 for example.  There is no way the DIO code can
> control
> > this gpio unless I modify the kernel to export the gpio name to what DIO
> > expects.  Can DIO change to allow the name of the exported gpio to be
> > passed in?
> >
> > Thanks,
> > Rob
>
>