From: Xiaobo Tian <peterwillcn@gmail.com>
To: robh+dt@kernel.org, heiko@sntech.de, jagan@amarulasolutions.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Xiaobo Tian <peterwillcn@gmail.com>
Subject: [PATCH 1/2] arm64: dts: rockchip: r4s: system status LEDs changed to flashing light
Date: Mon, 5 Jul 2021 23:03:26 +0800 [thread overview]
Message-ID: <20210705150327.86189-1-peterwillcn@gmail.com> (raw)
There are 4 LEDs on the motherboard, except for the power lamp,
which are LED-0 STATUS, LED-1 LAN, LED-2 WAN.
The LED-0 is repeatedly defined and therefore removed
and inherited the heartbeat status LED-0 using dtsi.
Signed-off-by: Xiaobo Tian <peterwillcn@gmail.com>
---
.../boot/dts/rockchip/rk3399-nanopi-r4s.dts | 45 +++++++------------
1 file changed, 15 insertions(+), 30 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
index fa5809887643..a0f928990fdd 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
@@ -1,14 +1,15 @@
// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
/*
- * FriendlyElec NanoPC-T4 board device tree source
- *
+ * Copyright (c) 2016 Fuzhou Rockchip Electronics Co., Ltd
* Copyright (c) 2020 FriendlyElec Computer Tech. Co., Ltd.
* (http://www.friendlyarm.com)
*
+ * Copyright (c) 2016 Arm Ltd.
* Copyright (c) 2018 Collabora Ltd.
*
* Copyright (c) 2020 Jensen Huang <jensenhuang@friendlyarm.com>
* Copyright (c) 2020 Marty Jones <mj8263788@gmail.com>
+ * Copyright (C) 2020 Xiaobo Tian <peterwillcn@gmail.com>
* Copyright (c) 2021 Tianling Shen <cnsztl@gmail.com>
*/
@@ -21,28 +22,6 @@ / {
/delete-node/ display-subsystem;
- gpio-leds {
- pinctrl-0 = <&lan_led_pin>, <&sys_led_pin>, <&wan_led_pin>;
-
- /delete-node/ led-0;
-
- lan_led: led-lan {
- gpios = <&gpio1 RK_PA1 GPIO_ACTIVE_HIGH>;
- label = "green:lan";
- };
-
- sys_led: led-sys {
- gpios = <&gpio0 RK_PB5 GPIO_ACTIVE_HIGH>;
- label = "red:sys";
- default-state = "on";
- };
-
- wan_led: led-wan {
- gpios = <&gpio1 RK_PA0 GPIO_ACTIVE_HIGH>;
- label = "green:wan";
- };
- };
-
gpio-keys {
pinctrl-0 = <&reset_button_pin>;
@@ -72,6 +51,18 @@ &i2c4 {
status = "disabled";
};
+&leds {
+ lan_led: led-1 {
+ gpios = <&gpio1 RK_PA1 GPIO_ACTIVE_HIGH>;
+ label = "green:lan";
+ };
+
+ wan_led: led-2 {
+ gpios = <&gpio1 RK_PA0 GPIO_ACTIVE_HIGH>;
+ label = "green:wan";
+ };
+};
+
&pcie0 {
max-link-speed = <1>;
num-lanes = <1>;
@@ -80,16 +71,10 @@ &pcie0 {
&pinctrl {
gpio-leds {
- /delete-node/ status-led-pin;
-
lan_led_pin: lan-led-pin {
rockchip,pins = <1 RK_PA1 RK_FUNC_GPIO &pcfg_pull_none>;
};
- sys_led_pin: sys-led-pin {
- rockchip,pins = <0 RK_PB5 RK_FUNC_GPIO &pcfg_pull_none>;
- };
-
wan_led_pin: wan-led-pin {
rockchip,pins = <1 RK_PA0 RK_FUNC_GPIO &pcfg_pull_none>;
};
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-07-05 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 15:03 Xiaobo Tian [this message]
2021-07-05 15:03 ` [PATCH 2/2] arm64: dts: rockchip: r4s: remove the vcc3v3 use vcc5v0 wrong supply voltage Xiaobo Tian
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=20210705150327.86189-1-peterwillcn@gmail.com \
--to=peterwillcn@gmail.com \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--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).