MIME-Version: 1.0
References: <CA+ryuvCuLS1Lwp=Bc17L1btm7g1u33YGdehNRJqrEexrv5gpCg@mail.gmail.com>
In-Reply-To: <CA+ryuvCuLS1Lwp=Bc17L1btm7g1u33YGdehNRJqrEexrv5gpCg@mail.gmail.com>
From: =?UTF-8?Q?David_Taill=C3=A9?= <david.taille.fr@gmail.com>
Date: Fri, 27 Dec 2019 19:28:17 +0100
Message-ID: <CA+ryuvBuyUfH-DbQ2jx0mexFBo0jGD0X0UFnSpBPpJBQF8hBZw@mail.gmail.com>
Subject: Re: 3.11.2 and RPi.GPIO 0.6.5 on Pi Zero : edge detection no longer working
To: ~alpine/devel@lists.alpinelinux.org
Content-Type: multipart/alternative; boundary="0000000000001a3416059ab3a943"

--0000000000001a3416059ab3a943
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Think i know what the problem is: 3.11 dropped support for deprecated sysfs
gpio in kernel, which breaks RPi.GPIO for edge detection.

Was this intentional ? Or is it just that the config from kernel has those
items turned off by default ?

Can't check right now, but i believe raspbian is still supporting sysfs
gpio.
Don't you think alpine had better support it as well for Pi devices ?

David


Le jeu. 26 d=C3=A9c. 2019 =C3=A0 23:39, David Taill=C3=A9 <david.taille.fr@=
gmail.com> a
=C3=A9crit :

> Hi all,
>
> I just installed Alpine 3.11.2 on a Pi Zero W, and just found RPi.GPIO no
> longer works for edge detection.
> Package installation :
> apk add python3
> apk add py3-rpigpio
>
> Test file :
> import RPi.GPIO as g
> pin=3D4
> g.setmode(g.BCM)
> print("pin%d mode is %d\n" % (pin, g.gpio_function(pin)))
> g.setup(pin, g.IN, pull_up_down=3Dg.PUD_DOWN)
> print("pin%d state=3D%d\n" % (pin, g.input(pin)))
> while True:
>    x =3D g.wait_for_edge(pin, g.BOTH)
>    print("pin%d edge %d\n" % (pin, x))
>
> On Alpine 3.10.0, it works as expected, printing a line as you bring pin =
4
> to ground or 3.3V.
> On Alpine 3.11.2, i get :
> # python3 testgpio.py
> function of pin 4 =3D 1
>
> pin 4 now is 0
> Traceback (most recent call last):
>   File "testgpio.py", line 8, in <module>
>     x =3D g.wait_for_edge(pin, g.BOTH)
> RuntimeError: Error waiting for edge
>
> Other methods such as add_event_detect also fail with a RuntimeError abou=
t
> being unable to add edge detection.
> Other tests I ran prove reading pins and setting pin state do work.
>
> lsmod shows :
> i2c_gpio               16384  0
> i2c_algo_bit           16384  1 i2c_gpio
>
> So,
> Which do you think is the culprit ? alpine or RPi.GPIO ?
> Who would you reach out to to get this fixed ? or at least examined ?
>
> Thanks for any feedback !
> David
>
>
>
>
>
>
>

--0000000000001a3416059ab3a943
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi,<div dir=3D"auto"><br></div><div dir=3D"auto">Think i =
know what the problem is: 3.11 dropped support for deprecated sysfs gpio in=
 kernel, which breaks RPi.GPIO for edge detection.</div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Was this intentional ? Or is it just that the co=
nfig from kernel has those items turned off by default ?</div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">Can&#39;t check right now, but i believe r=
aspbian is still supporting sysfs gpio.</div><div dir=3D"auto">Don&#39;t yo=
u think alpine had better support it as well for Pi devices ?=C2=A0</div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto">David=C2=A0</div><div dir=3D"au=
to"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">Le jeu. 26 d=C3=A9c. 2019 =C3=A0 23:39, David Taill=C3=A9 &=
lt;<a href=3D"mailto:david.taille.fr@gmail.com">david.taille.fr@gmail.com</=
a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div>Hi all,</div><div><br></div><div>I just installed Alpine 3.11=
.2 on a Pi Zero W, and just found RPi.GPIO no longer works for edge detecti=
on.</div><div>Package installation :<br></div><div>apk add python3</div><di=
v>apk add py3-rpigpio</div><div><br></div><div>Test file :</div><div style=
=3D"margin-left:40px"><span style=3D"font-family:monospace">import RPi.GPIO=
 as g<br>pin=3D4<br>g.setmode(g.BCM)<br>print(&quot;pin%d mode is %d\n&quot=
; % (pin, g.gpio_function(pin)))<br>g.setup(pin, g.IN, pull_up_down=3Dg.PUD=
_DOWN)<br>print(&quot;pin%d state=3D%d\n&quot; % (pin, g.input(pin)))<br>wh=
ile True:<br>=C2=A0=C2=A0	x =3D g.wait_for_edge(pin, g.BOTH)<br>=C2=A0=C2=
=A0	print(&quot;pin%d edge %d\n&quot; % (pin, x))</span></div><div><br></di=
v><div>On Alpine 3.10.0, it works as expected, printing a line as you bring=
 pin 4 to ground or 3.3V.<br></div><div>On Alpine 3.11.2, i get :</div><div=
 style=3D"margin-left:40px"><span style=3D"font-family:monospace"># python3=
 testgpio.py <br>function of pin 4 =3D 1<br><br>pin 4 now is 0<br>Traceback=
 (most recent call last):<br>=C2=A0 File &quot;testgpio.py&quot;, line 8, i=
n &lt;module&gt;<br>=C2=A0 =C2=A0 x =3D g.wait_for_edge(pin, g.BOTH)<br>Run=
timeError: Error waiting for edge</span></div><div><br></div><div>Other met=
hods such as add_event_detect also fail with a RuntimeError about being una=
ble to add edge detection.</div><div>Other tests I ran prove reading pins a=
nd setting pin state do work.</div><div><br></div><div>lsmod shows :</div><=
div><span style=3D"font-family:monospace">i2c_gpio =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 16384 =C2=A00 <br>i2c_algo_bit =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 16384 =C2=A01 i2c_gpio<br></span></div><div><br></div><di=
v>So,</div><div>Which do you think is the culprit ? alpine or RPi.GPIO ?</d=
iv><div>Who would you reach out to to get this fixed ? or at least examined=
 ?</div><div><br></div><div>Thanks for any feedback !<br></div><div>David</=
div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></=
div><div><br></div></div>
</blockquote></div>

--0000000000001a3416059ab3a943--