From: Xiaobo Tian <peterwillcn@gmail.com>
To: u-boot@lists.denx.de, kever.yang@rock-chips.com
Cc: Xiaobo Tian <peterwillcn@gmail.com>
Subject: [PATCH 1/4] arm64: rk3399: r4s: correct the LEDS label name
Date: Tue, 6 Jul 2021 22:43:57 +0800 [thread overview]
Message-ID: <20210706144400.8665-1-peterwillcn@gmail.com> (raw)
Correct the LEDS label name and remove the board type prefix,
which is actually unnecessary here, removes the redefined system status LED pin.
Signed-off-by: Xiaobo Tian <peterwillcn@gmail.com>
---
arch/arm/dts/rk3399-nanopi-r4s.dts | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/arm/dts/rk3399-nanopi-r4s.dts b/arch/arm/dts/rk3399-nanopi-r4s.dts
index 6f2cf17bf1..7470c26820 100644
--- a/arch/arm/dts/rk3399-nanopi-r4s.dts
+++ b/arch/arm/dts/rk3399-nanopi-r4s.dts
@@ -76,18 +76,17 @@
&leds {
lan_led: led-1 {
gpios = <&gpio1 RK_PA1 GPIO_ACTIVE_HIGH>;
- label = "nanopi-r4s:green:lan";
+ label = "green:lan";
};
wan_led: led-2 {
gpios = <&gpio1 RK_PA0 GPIO_ACTIVE_HIGH>;
- label = "nanopi-r4s:green:wan";
+ label = "green:wan";
};
};
&leds_gpio {
rockchip,pins =
- <0 RK_PB5 RK_FUNC_GPIO &pcfg_pull_none>,
<1 RK_PA0 RK_FUNC_GPIO &pcfg_pull_none>,
<1 RK_PA1 RK_FUNC_GPIO &pcfg_pull_none>;
};
--
2.32.0
next reply other threads:[~2021-07-06 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 14:43 Xiaobo Tian [this message]
2021-07-06 14:43 ` [PATCH 2/4] arm64: rk3399: r4s: Inheritance uses the sdmmc definition in dtsi Xiaobo Tian
2021-08-11 10:07 ` Kever Yang
2021-07-06 14:43 ` [PATCH 3/4] arm64: rk3399: r4s: Remove undesirable MAC address fetching methods for ethernet Xiaobo Tian
2021-08-11 10:07 ` Kever Yang
2021-07-06 14:44 ` [PATCH 4/4] arm64: rk3399: r4s: disabled i2c4 bus during the system boot process Xiaobo Tian
2021-08-11 10:10 ` Kever Yang
2021-08-11 10:06 ` [PATCH 1/4] arm64: rk3399: r4s: correct the LEDS label name Kever Yang
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=20210706144400.8665-1-peterwillcn@gmail.com \
--to=peterwillcn@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=u-boot@lists.denx.de \
/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