From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Fabien Dessenne <fabien.dessenne@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
<devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: stm32: add blue led (Linux heartbeat) on stm32mp135f-dk
Date: Tue, 3 May 2022 15:48:29 +0200 [thread overview]
Message-ID: <e1934106-85cb-58ab-83db-a4394982f36c@foss.st.com> (raw)
In-Reply-To: <20220503094124.502416-1-fabien.dessenne@foss.st.com>
On 5/3/22 11:41, Fabien Dessenne wrote:
> The blue led (Linux heartbeat) is connected to the PA14 pin of the
> stm32mp135f-dk board.
>
> Signed-off-by: Fabien Dessenne <fabien.dessenne@foss.st.com>
> ---
> arch/arm/boot/dts/stm32mp135f-dk.dts | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp135f-dk.dts b/arch/arm/boot/dts/stm32mp135f-dk.dts
> index aefa25ee897d..65acee0f68b7 100644
> --- a/arch/arm/boot/dts/stm32mp135f-dk.dts
> +++ b/arch/arm/boot/dts/stm32mp135f-dk.dts
> @@ -6,6 +6,8 @@
>
> /dts-v1/;
>
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/leds/common.h>
> #include "stm32mp135.dtsi"
> #include "stm32mp13xf.dtsi"
> #include "stm32mp13-pinctrl.dtsi"
> @@ -23,6 +25,18 @@ memory@c0000000 {
> reg = <0xc0000000 0x20000000>;
> };
>
> + leds {
> + compatible = "gpio-leds";
> +
> + led-blue {
> + function = LED_FUNCTION_HEARTBEAT;
> + color = <LED_COLOR_ID_BLUE>;
> + gpios = <&gpioa 14 GPIO_ACTIVE_LOW>;
> + linux,default-trigger = "heartbeat";
> + default-state = "off";
> + };
> + };
> +
> vdd_sd: vdd-sd {
> compatible = "regulator-fixed";
> regulator-name = "vdd_sd";
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2022-05-03 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 9:41 [PATCH 1/2] ARM: dts: stm32: add blue led (Linux heartbeat) on stm32mp135f-dk Fabien Dessenne
2022-05-03 13:48 ` 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=e1934106-85cb-58ab-83db-a4394982f36c@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@foss.st.com \
--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+dt@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;
as well as URLs for NNTP newsgroup(s).