Study of a possible implementation of gpiozero to support RPI5

[outdoorbits]

This is just a study of a possible implementation of gpiozero to support the Raspberry Pi 5 in the future. Up to now I didn't step deep enough into your code to really understand it. So I couldn't test it yet. But I think this could be an easy way to migrate from RPi.GPIO to gpiozero. The advantage would be to have one library (gpiozero) which is compatible to both, Raspberry Pi 4 (and older) and Raspberry Pi 5 (and hopefully others in future).

refs #268

[thijstriemstra]

thanks! I saw another project (moonraker) that switched to https://pypi.org/project/python-periphery, maybe an option as well..

[outdoorbits]

But the last commit of python-periphery is much older than the RPi 5, so it won't be able to support its new hardware.

[thijstriemstra]

But the last commit of python-periphery is much older than the RPi 5, so it won't be able to support its new hardware.

Not sure, as long as it supports the linux kernel gpio interface (around for years), it should be fine since that is what the rpi5 uses afaik.

[outdoorbits]

I don't think python-periphery works. I tested inputs:

from gpiozero import Button
from signal import pause

def pressed():
        print('+')

def released():
        print('-')


button = Button(26,pull_up=False)

button.when_pressed = pressed
button.when_released = released

pause()

works fine while

from periphery import GPIO
import time

# Open GPIO /dev/gpiochip0 line 10 with input direction
gpio_in = GPIO("/dev/gpiochip0", 26, "in")
# Open GPIO /dev/gpiochip0 line 12 with output direction
gpio_out = GPIO("/dev/gpiochip0", 12, "out")

while True:
        print(gpio_in.read())
        time.sleep(1)

gpio_out.write(not value)

gpio_in.close()
gpio_out.close()

didn't work.