[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <64349026443d6178487db34233d24478821a1ca1.camel@codeconstruct.com.au>
Date: Wed, 03 Dec 2025 16:25:29 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: alex.ts.wang@...-foxconn.com, Rob Herring <robh@...nel.org>, Krzysztof
Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Joel
Stanley <joel@....id.au>
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
Subject: Re: [PATCH v2] dt: aspeed: clemente: move hdd_led to its own
gpio-leds group
On Thu, 2025-11-27 at 17:44 +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 not available the whole group will not be
> created. 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.
>
> Signed-off-by: Alex Wang <alex.ts.wang@...-foxconn.com>
I've applied this, however, I fixed the subject so it has the usual
'ARM: dts: aspeed:' prefix, and added the following Fixes tag:
Fixes: b5dd16228216 ("ARM: dts: aspeed: clemente: Add HDD LED GPIO")
Andrew
Powered by blists - more mailing lists