From: Alexander Dahl <ada@thorsis.com>
To: Ryan.Wanner@microchip.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: microchip: sama7d65: Add GPIO buttons and LEDs
Date: Wed, 10 Sep 2025 08:25:14 +0200 [thread overview]
Message-ID: <20250910-alkalize-overtime-930a59a7d169@thorsis.com> (raw)
In-Reply-To: <20250910-retake-attic-ac1fe3429a1e@thorsis.com>
Hello Ryan,
Am Wed, Sep 10, 2025 at 08:20:28AM +0200 schrieb Alexander Dahl:
> Hello Ryan,
>
> Am Tue, Sep 09, 2025 at 09:08:38AM -0700 schrieb Ryan.Wanner@microchip.com:
> > From: Ryan Wanner <Ryan.Wanner@microchip.com>
> >
> > Add the USER button as a GPIO input as well as add the LEDs and enable
> > the blue LED as a heartbeat.
> >
> > Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
> > ---
> > .../dts/microchip/at91-sama7d65_curiosity.dts | 49 +++++++++++++++++++
> > 1 file changed, 49 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/microchip/at91-sama7d65_curiosity.dts b/arch/arm/boot/dts/microchip/at91-sama7d65_curiosity.dts
> > index f091cc40a9f0..2fe34c59d942 100644
> > --- a/arch/arm/boot/dts/microchip/at91-sama7d65_curiosity.dts
> > +++ b/arch/arm/boot/dts/microchip/at91-sama7d65_curiosity.dts
> > @@ -11,6 +11,7 @@
> > #include "sama7d65-pinfunc.h"
> > #include "sama7d65.dtsi"
> > #include <dt-bindings/mfd/atmel-flexcom.h>
> > +#include <dt-bindings/input/input.h>
> > #include <dt-bindings/pinctrl/at91.h>
> >
> > / {
> > @@ -26,6 +27,42 @@ chosen {
> > stdout-path = "serial0:115200n8";
> > };
> >
> > + gpio-keys {
> > + compatible = "gpio-keys";
> > +
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_key_gpio_default>;
> > +
> > + button {
> > + label = "PB_USER";
> > + gpios = <&pioa PIN_PC10 GPIO_ACTIVE_LOW>;
> > + linux,code = <KEY_PROG1>;
> > + wakeup-source;
> > + };
> > + };
> > +
> > + leds {
> > + compatible = "gpio-leds";
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_led_gpio_default>;
> > +
> > + led-red {
> > + label = "red";
> > + gpios = <&pioa PIN_PB17 GPIO_ACTIVE_HIGH>; /* Conflict with pwm. */
> > + };
> > +
> > + led-green {
> > + label = "green";
> > + gpios = <&pioa PIN_PB15 GPIO_ACTIVE_HIGH>; /* Conflict with pwm. */
> > + };
> > +
> > + led-blue {
> > + label = "blue";
> > + gpios = <&pioa PIN_PA21 GPIO_ACTIVE_HIGH>;
> > + linux,default-trigger = "heartbeat";
> > + };
> > + };
>
> The label property is deprecated. Please use the properties "color"
> and "function" for new boards. See devicetree binding documentation
> for LEDs.
From a quick glance, this seems to be an RGB-LED, so I would suggest
to not model it as three distinct LEDs, but make use of the
"leds-group-multicolor" feature, example:
59 multi-led {
60 compatible = "leds-group-multicolor";
61 color = <LED_COLOR_ID_RGB>;
62 function = LED_FUNCTION_INDICATOR;
63 leds = <&led_red>, <&led_green>, <&led_blue>;
64 };
Greets
Alex
>
> Thanks and greetings
> Alex
>
> > +
> > memory@60000000 {
> > device_type = "memory";
> > reg = <0x60000000 0x40000000>;
> > @@ -352,6 +389,18 @@ pinctrl_i2c10_default: i2c10-default {
> > bias-pull-up;
> > };
> >
> > + pinctrl_key_gpio_default: key-gpio-default {
> > + pinmux = <PIN_PC10__GPIO>;
> > + bias-pull-up;
> > + };
> > +
> > + pinctrl_led_gpio_default: led-gpio-default {
> > + pinmux = <PIN_PB15__GPIO>,
> > + <PIN_PB17__GPIO>,
> > + <PIN_PA21__GPIO>;
> > + bias-pull-up;
> > + };
> > +
> > pinctrl_sdmmc1_default: sdmmc1-default {
> > cmd-data {
> > pinmux = <PIN_PB22__SDMMC1_CMD>,
> > --
> > 2.43.0
> >
> >
>
next prev parent reply other threads:[~2025-09-10 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 16:08 [PATCH] ARM: dts: microchip: sama7d65: Add GPIO buttons and LEDs Ryan.Wanner
2025-09-10 6:20 ` Alexander Dahl
2025-09-10 6:25 ` Alexander Dahl [this message]
2025-09-10 17:16 ` Ryan Wanner
2025-09-11 7:00 ` Alexander Dahl
2025-09-16 17:38 ` Ryan Wanner
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=20250910-alkalize-overtime-930a59a7d169@thorsis.com \
--to=ada@thorsis.com \
--cc=Ryan.Wanner@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.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