Date: Tue, 18 Aug 2020 09:26:39 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 189772] [NEW DRIVER] apuled(4): LED driver on PC Engines APU (1/2/3) boards Message-ID: <bug-189772-227-waUGKiwTj8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-189772-227@https.bugs.freebsd.org/bugzilla/> References: <bug-189772-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D189772 --- Comment #10 from Andriy Gapon <avg@FreeBSD.org> --- My personal opinion. The gpio controller on APU2 is the standard AMD GPIO controller. With the latest firmware it is advertised via ACPI, so amdgpu driver can at= tach perfectly well and gpioctl can be used to control the LEDs and query the switch. Of course, that is not convenient at all. But the latest firmware also describes the LEDs and the switch via ACPI. So, we need some glue to parse the ACPI description and attach the standard gpioled and gpiokeys drivers under amdgpu. That would be very similar to what is done on FDT based systems. I think that such approach would be more extensible than hardcoding everyth= ing is a platform specific driver. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-189772-227-waUGKiwTj8>