Re: port-evbarm/59572: gpioleds does not detect ACT on RPi 3B 1.2

["Michael van Elst via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR port-evbarm/59572; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-evbarm/59572: gpioleds does not detect ACT on RPi 3B 1.2
Date: Mon, 4 Aug 2025 21:35:26 -0000 (UTC)

 schmonz%NetBSD.org@localhost writes:
 
 >On a Raspberry Pi Model B Rev 2, dmesg shows
 >    gpioleds0 at simplebus0: ACT
 >And, as expected, I can make the LED turn on with `sysctl -w hw.led.ACT=1`.
 
 >On a Raspberry Pi 3 Model B Rev 1.2, dmesg shows
 >    gpioleds0 at simplebus0: 
 >And there's no way I'm aware of to manipulate the LED (`sysctl:
 >second level name 'led' in 'hw.led.ACT' is invalid`).
 
 
 On the Pi 3 there is no GPIO you could use to control the LED.
 If I didn't make a mistake, this is how the various models
 control the two LEDs:
 
 MODEL  PWR     ACT
 pi0    none    GPIO47
 pi1    3.3V    GPIO16
 pi1+   GPIO35  GPIO47
 pi2    GPIO35  GPIO47
 pi3    VCmbox  virtgpio
 pi3+   VCmbox  GPIO29
 pi4    VCmbox  GPIO42
 
 
 virtgpio emulates a simple (output only) GPIO port
 by mapping a memory page that is polled by the GPU
 to control the LED, and we currently lack a driver
 for that.