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

[schmonz%NetBSD.org@localhost]

>Number:         59572
>Category:       port-evbarm
>Synopsis:       gpioleds does not detect ACT on RPi 3B 1.2
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-evbarm-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 04 20:25:00 +0000 2025
>Originator:     Amitai Schleier
>Release:        NetBSD 10.1
>Organization:
Schmonz Enterprises
>Environment:
System: NetBSD rpi3b12.schmonz.local 10.1 NetBSD 10.1 (GENERIC64) #0: Mon Dec 16 13:08:11 UTC 2024  mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/evbarm/compile/GENERIC64 evbarm
Architecture: aarch64
Machine: evbarm
>Description:
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`).

>How-To-Repeat:
Boot up and try to fiddle with the blinkenlights.
>Fix:
None known.