From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Leo Wang <leo.jt.wang@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
george.kw.lee@fii-foxconn.com, bruce.jy.hung@fii-foxconn.com,
leo.jt.wang@fii-foxconn.com
Subject: Re: [PATCH] ARM: dts: aspeed: clemente: Add HDD LED GPIO
Date: Mon, 29 Sep 2025 12:30:41 +0930 [thread overview]
Message-ID: <deb2dda58b923f2ae362dc19164dc845c4757e12.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250926-leo-dts-add-shunt-resistor-v1-1-c871a68792f0@gmail.com>
Hi Leo,
On Fri, 2025-09-26 at 17:37 +0800, Leo Wang wrote:
> Define a GPIO expander pin for the HDD LED and expose it via the
> LED subsystem. This allows the BMC to control the front panel
> HDD activity LED.
>
> Changes include:
> - Add `led-hdd` node under the LED definitions
> - Name the expander pin "HDD_LED_N" in io_expander13
Can you please drop this "Changes include" section? What you've written
here is plain to see from the diff below. The commit message should
explain motivations, concerns and trade-offs, and not be a wrote
description of the change. The documentation on submitting patches
explores what's required:
https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
Cheers,
Andrew
>
> Signed-off-by: Leo Wang <leo.jt.wang@gmail.com>
> ---
> arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts
> index a614f947dafc9a6628c3f3d45b62ff3ca9d2b618..450446913e36b1418fab901cde44280468990c7a 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts
> @@ -95,6 +95,11 @@ led-3 {
> label = "bmc_ready_cpld_noled";
> gpios = <&gpio0 ASPEED_GPIO(P, 5) (GPIO_ACTIVE_HIGH|GPIO_TRANSITORY)>;
> };
> +
> + led-hdd {
> + label = "hdd_led";
> + gpios = <&io_expander13 1 GPIO_ACTIVE_LOW>;
> + };
> };
>
> memory@80000000 {
> @@ -1199,7 +1204,7 @@ io_expander13: gpio@14 {
> #gpio-cells = <2>;
> gpio-line-names =
> "rmc_en_dc_pwr_on",
> - "",
> + "HDD_LED_N",
> "",
> "",
> "",
>
> ---
> base-commit: c65261717599d419e9c683d85f515d3ca2261549
> change-id: 20250926-leo-dts-add-shunt-resistor-0cba43f75bce
>
> Best regards,
prev parent reply other threads:[~2025-09-29 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 9:37 Leo Wang
2025-09-29 3:00 ` Andrew Jeffery [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=deb2dda58b923f2ae362dc19164dc845c4757e12.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=bruce.jy.hung@fii-foxconn.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.kw.lee@fii-foxconn.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=leo.jt.wang@fii-foxconn.com \
--cc=leo.jt.wang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®