Re: GPIO offsets used by userspace

[Andrew Jeffery <andrew@aj.id.au>]

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On Wed, 2017-02-01 at 09:55 +1030, Joel Stanley wrote:
> > I mentioned this on GitHub, but in theory we should have at least one
> > /sys/class/gpio/gpiochipN directory, where N is the offset for GPIOs
> > provided by that GPIO device.
> >
> > On a BMC not attached to GPIO expanders this directory name could be
> > parsed by the Python currently in use. Not foolproof, but it could be
> > a working stopgap.
> 
> You're right, we could find this one. This would break on Witherspoon
> though which will soon gain a driver for a GPIO expander.
> 
> We could write some python to iterate through the gpiochipN
> directories, and match against the label:
> 
> root@zaius5:~# cat /sys/class/gpio/gpiochip320/label
> 1e780000.gpio
> 
> This would be a stopgap until we could get something saner, like sysfs
> files named after the net or function.

If we're going to change things so significantly we should move away
from using sysfs given it's deprecated, even if the alternative isn't
great.

Andrew

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]