From: Artem Lapkin <email2tema@gmail.com>
To: narmstrong@baylibre.com
Cc: devicetree@vger.kernel.org, gouwa@khadas.com,
martin.blumenstingl@googlemail.com, khilman@baylibre.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
nick@khadas.com, linux-amlogic@lists.infradead.org,
art@khadas.com, linux-arm-kernel@lists.infradead.org,
jbrunet@baylibre.com
Subject: [PATCH 1/2] arm64: dts: meson: rename led name on Khadas VIM2 meson-gxm-khadas-vim2
Date: Mon, 28 Sep 2020 17:26:12 +0800 [thread overview]
Message-ID: <20200928092613.273998-2-art@khadas.com> (raw)
In-Reply-To: <20200928092613.273998-1-art@khadas.com>
rename led name on Khadas VIM2 meson-gxm-khadas-vim2
rename vim:red:power to vim2:white:sys
becouse this led is white system led its not power led
Signed-off-by: Artem Lapkin <art@khadas.com>
---
arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts b/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts
index bff8ec2c1c7..624632f06b5 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts
@@ -84,8 +84,8 @@ hdmi_connector_in: endpoint {
pwmleds {
compatible = "pwm-leds";
- power {
- label = "vim:red:power";
+ system {
+ label = "vim2:white:sys";
pwms = <&pwm_AO_ab 1 7812500 0>;
max-brightness = <255>;
linux,default-trigger = "default-on";
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-28 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 9:26 [PATCH v2 0/2] arm64: dts: meson: VIM2 updates Artem Lapkin
2020-09-28 9:26 ` Artem Lapkin [this message]
2020-09-28 9:26 ` [PATCH 2/2] arm64: dts: meson: change spifc max-frequency on Khadas VIM2 meson-gxm-khadas-vim2 Artem Lapkin
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=20200928092613.273998-2-art@khadas.com \
--to=email2tema@gmail.com \
--cc=art@khadas.com \
--cc=devicetree@vger.kernel.org \
--cc=gouwa@khadas.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=nick@khadas.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).