
Andreas Färber wrote:
Hi Matthias and Peter,
Raspberry Pi have a downstream patch that's hardcoding numbers to align with their schematics or whatever. That's not acceptable to upstream.
Ah, that explains it. (And I agree we should stick with upstream...)
In fact there is a gpio-fan binding that might just be used here:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Doc...
Interesting! Thanks for the link - I'll have avery close look at it :)
Also, the sysfs GPIO interface is documented as obsolete, so with Factory it may break at some point.
I had only used it to verify HW is working, and as that had failed, too, I got nervous...
libgpiod is the designated replacement since multiple years.
So we only need to communicate that to "the others" *eg*
https://build.opensuse.org/package/show/hardware/libgpiod
Not familiar with which of the interfaces which Python packages consume.
My (remote) tests with python3-gpiod indicate everything works fine. I'll verify tomorrow when I'm (physically) at the Pi again.