From: Andrei Simion <andrei.simion@microchip.com>
To: <conor@kernel.org>
Cc: <ada@thorsis.com>, <alexandre.belloni@bootlin.com>,
<andrei.simion@microchip.com>, <claudiu.beznea@tuxon.dev>,
<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<krzk+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <nicolas.ferre@microchip.com>,
<robh@kernel.org>
Subject: Re: [PATCH v2 4/4] ARM: dts: microchip: aks-cdu: Add label for LED sub nodes
Date: Wed, 2 Oct 2024 13:30:45 +0300 [thread overview]
Message-ID: <20241002103044.108413-1-andrei.simion@microchip.com> (raw)
In-Reply-To: <20241001-sleet-bronchial-867258945373@spud>
> On Tue, Oct 01, 2024 at 06:25:41PM +0300, Andrei Simion wrote:
>> Add the label property here and use the old node name as value to stay
>> stable and avoid breaking the userspace applications that depend on those
>> paths.
>>
>> Suggested-by: Alexander Dhal <ada@thorsis.com>
>> Signed-off-by: Andrei Simion <andrei.simion@microchip.com>
> Shouldn't this be squashed with 3/4 so as not to break it in one commit,
> only to fix it in another?
>
Hi,
My intent here was to give credits.
If this approach is unnecessary, I will do squash in V3.
Best Regards,
Andrei Simion
>> ---
>> v1 -> v2:
>> - added in v2 by suggestion of Alexander Dhal
>> ---
>> arch/arm/boot/dts/microchip/aks-cdu.dts | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/microchip/aks-cdu.dts b/arch/arm/boot/dts/microchip/aks-cdu.dts
>> index 0c3373ad1723..b65f80e1ef05 100644
>> --- a/arch/arm/boot/dts/microchip/aks-cdu.dts
>> +++ b/arch/arm/boot/dts/microchip/aks-cdu.dts
>> @@ -99,22 +99,26 @@ leds {
>> compatible = "gpio-leds";
>>
>> led-red {
>> + label = "red";
>> gpios = <&pioC 10 GPIO_ACTIVE_HIGH>;
>> linux,default-trigger = "none";
>> };
>>
>> led-green {
>> + label = "green";
>> gpios = <&pioA 5 GPIO_ACTIVE_LOW>;
>> linux,default-trigger = "none";
>> default-state = "on";
>> };
>>
>> led-yellow {
>> + label = "yellow";
>> gpios = <&pioB 20 GPIO_ACTIVE_LOW>;
>> linux,default-trigger = "none";
>> };
>>
>> led-blue {
>> + label = "blue";
>> gpios = <&pioB 21 GPIO_ACTIVE_LOW>;
>> linux,default-trigger = "none";
>> };
>> --
>> 2.34.1
next prev parent reply other threads:[~2024-10-02 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 15:25 [PATCH v2 0/4] Cosmetic Work for ARM/Microchip (AT91) Andrei Simion
2024-10-01 15:25 ` [PATCH v2 1/4] ARM: dts: microchip: Rename the eeprom nodename Andrei Simion
2024-10-01 15:25 ` [PATCH v2 2/4] ARM: dts: microchip: Rename the pmic node Andrei Simion
2024-10-01 15:25 ` [PATCH v2 3/4] ARM: dts: microchip: Rename LED sub nodes name Andrei Simion
2024-10-01 15:25 ` [PATCH v2 4/4] ARM: dts: microchip: aks-cdu: Add label for LED sub nodes Andrei Simion
2024-10-01 15:31 ` Conor Dooley
2024-10-02 10:30 ` Andrei Simion [this message]
2024-10-02 10:42 ` Alexander Dahl
2024-10-02 3:52 ` [PATCH v2 0/4] Cosmetic Work for ARM/Microchip (AT91) Rob Herring (Arm)
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=20241002103044.108413-1-andrei.simion@microchip.com \
--to=andrei.simion@microchip.com \
--cc=ada@thorsis.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=conor@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;
as well as URLs for NNTP newsgroup(s).