Guillaume Gardet wrote:
> > -----Original Message-----
> > From: Guillaume Gardet <[email protected]>
> > Did you have a look at https://en.opensuse.org/openSUSE:GPIO for standard
> > packages to access GPIO instead of downstream, RPi specific, software?
Ah no - I saw that there is a different gpio package, and installed it, but
had no clue how to use it :(
So I first had a try at the 'basic /sys method'..
> >
> > You can use 'gpioinfo gpiochip446' and 'gpioinfo gpiochip454' to get info
> > about the
> > gpio available.
Actually 'gpiochip0' and 'gpiochip1'. But yes, that indeed does the trick.
Reading further explains also why I failed with /sys:
Note that the base, which is the N from /sys/class/gpio/gpiochipN, must be
added to the GPIO number. This is never mentioned because on Raspbian N is 0.
So indeed a bit irritating with the implementation that it lists
/sys/class/gpio/gpiochip446 and /sys/class/gpio/gpiochip454
but refers to them as gpiochip0 and gpiochip1 in gpioinfo whereas the /sys
interface requires the 446/454 offsets. I'd assume that is a kernel thing?
> And latest released Tumbleweed (20210901) test in openQA shows gpiochips 0
> and 1:
> gpiochip0 [pinctrl-bcm2711] (58 lines)
> gpiochip1 [raspberrypi-exp-gpio] (8 lines)
Indeed, that's what I see here, too :D
I'm physically away from the Pi, so I cannot verify that the output actually
gets 'high' - but I'm very confident it does.
Thanks for getting me on the right track!
