From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
<linux-kernel@vger.kernel.org>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 2/2] ARM: dts: stm32: add usr3 LED node to stm32f769-disco
Date: Thu, 27 Feb 2025 09:38:27 +0100 [thread overview]
Message-ID: <ea295010-136c-419a-80ff-3cdd0701fbd8@foss.st.com> (raw)
In-Reply-To: <20250217114513.1098844-2-dario.binacchi@amarulasolutions.com>
On 2/17/25 12:45, Dario Binacchi wrote:
> As indicated by the board silkscreen, there are three user LEDs.
> Add the missing one.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
>
> arch/arm/boot/dts/st/stm32f769-disco.dts | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm/boot/dts/st/stm32f769-disco.dts b/arch/arm/boot/dts/st/stm32f769-disco.dts
> index d52e36aedcfb..535cfdc4681c 100644
> --- a/arch/arm/boot/dts/st/stm32f769-disco.dts
> +++ b/arch/arm/boot/dts/st/stm32f769-disco.dts
> @@ -86,6 +86,9 @@ led-usr2 {
> led-usr1 {
> gpios = <&gpioj 13 GPIO_ACTIVE_HIGH>;
> };
> + led-usr3 {
> + gpios = <&gpioa 12 GPIO_ACTIVE_HIGH>;
> + };
> };
>
> gpio-keys {
Series applied on stm32-next.
Thanks
Alex
prev parent reply other threads:[~2025-02-27 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:45 [PATCH 1/2] ARM: dts: stm32: rename LEDs nodes for stm32f769-disco Dario Binacchi
2025-02-17 11:45 ` [PATCH 2/2] ARM: dts: stm32: add usr3 LED node to stm32f769-disco Dario Binacchi
2025-02-27 8:38 ` Alexandre TORGUE [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=ea295010-136c-419a-80ff-3cdd0701fbd8@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--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®