[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0118d17eb884ee664a035d44ddbbec56a418e353.camel@codeconstruct.com.au>
Date: Fri, 14 Nov 2025 14:27:16 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: alex.ts.wang@...-foxconn.com
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
george.kw.lee@...-foxconn.com, Rob Herring <robh@...nel.org>, Krzysztof
Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Joel
Stanley <joel@....id.au>
Subject: Re: [PATCH] dt: aspeed: clemente: move hdd_led to its own gpio-leds
group
On Thu, 2025-10-23 at 18:26 +0800, Alex Wang via B4 Relay wrote:
> From: Alex Wang <alex.ts.wang@...-foxconn.com>
>
> The gpio-leds driver requires all GPIOs in a group to be available;
> if any GPIO in the group is missing the whole group will not be
> created.
>
To me its behaviour appears inconsistent. Contrast:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/leds/leds-gpio.c?h=v6.18-rc1#n176
with
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/leds/leds-gpio.c?h=v6.18-rc1#n281
The driver should probably pick one policy or the other?
> The hdd_led GPIO is only present after standby power is
> enabled, which can prevent other LEDs in the same group from being
> created and blocks properly setting 'bmc_ready_noled'.
>
> Move the 'hdd_led' node into a separate gpio-leds group so that other
> LEDs are not blocked and the 'bmc_ready_noled' flag can be set
> correctly.
How is standby power applied? What are you doing to enable the use of
hdd-leds once that occurs?
Andrew
Powered by blists - more mailing lists