NetBSD Problem Report #59572

From schmonz@schmonz.com  Mon Aug  4 20:23:56 2025
Return-Path: <schmonz@schmonz.com>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits)
	 client-signature RSA-PSS (2048 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 359B71A923A
	for <gnats-bugs@gnats.NetBSD.org>; Mon,  4 Aug 2025 20:23:56 +0000 (UTC)
Message-Id: <20250804200327.16692.qmail@miracle-dirt.schmonz.com>
Date: 4 Aug 2025 20:03:27 -0000
From: schmonz@NetBSD.org
Reply-To: schmonz@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: gpioleds does not detect ACT on RPi 3B 1.2
X-Send-Pr-Version: 3.95

>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
>Last-Modified:  Mon Aug 04 21:40:01 +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:/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.

>Release-Note:

>Audit-Trail:

From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
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 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.

>Unformatted:

Home	PR Database Search