From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: robh@kernel.org, heiko@sntech.de, ezequiel@collabora.com,
xuwei5@hisilicon.com, michal.simek@xilinx.com, pavel@ucw.cz,
andy.gross@linaro.org
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
daniel.thompson@linaro.org, amit.kucheria@linaro.org,
linus.walleij@linaro.org, koen.kooi@linaro.org,
nicolas.dechesne@linaro.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: [PATCH v3 6/7] arm64: dts: xilinx: ultra96: Standardize LED labels and triggers
Date: Mon, 29 Oct 2018 15:12:44 +0530 [thread overview]
Message-ID: <20181029094245.7886-7-manivannan.sadhasivam@linaro.org> (raw)
In-Reply-To: <20181029094245.7886-1-manivannan.sadhasivam@linaro.org>
For all 96Boards, the following standard is used for onboard LEDs.
green:user1 default-trigger: heartbeat
green:user2 default-trigger: mmc0/disk-activity(onboard-storage)
green:user3 default-trigger: mmc1 (SD-card)
green:user4 default-trigger: none, panic-indicator
yellow:wlan default-trigger: phy0tx
blue:bt default-trigger: hci0-power
So lets adopt the same for Ultra96, which is one of the 96Boards
CE and AI platform. Since the WLAN and BT LEDs are hardwired onboard,
consolidate only User LEDs.
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
---
arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts b/arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts
index eb5e8bddb610..c08a8753215b 100644
--- a/arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts
+++ b/arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts
@@ -57,29 +57,30 @@
leds {
compatible = "gpio-leds";
ds2 {
- label = "ds2";
+ label = "green:user1";
gpios = <&gpio 20 GPIO_ACTIVE_HIGH>;
linux,default-trigger = "heartbeat";
};
ds3 {
- label = "ds3";
+ label = "green:user2";
gpios = <&gpio 19 GPIO_ACTIVE_HIGH>;
- linux,default-trigger = "phy0tx"; /* WLAN tx */
+ linux,default-trigger = "mmc0";
default-state = "off";
};
ds4 {
- label = "ds4";
+ label = "green:user3";
gpios = <&gpio 18 GPIO_ACTIVE_HIGH>;
- linux,default-trigger = "phy0rx"; /* WLAN rx */
+ linux,default-trigger = "mmc1";
default-state = "off";
};
ds5 {
- label = "ds5";
+ label = "green:user4";
gpios = <&gpio 17 GPIO_ACTIVE_HIGH>;
- linux,default-trigger = "bluetooth-power";
+ linux,default-trigger = "none";
+ panic-indicator;
};
vbus_det { /* U5 USB5744 VBUS detection via MIO25 */
--
2.17.1
next prev parent reply other threads:[~2018-10-29 9:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 9:42 [PATCH v3 0/7] Standardize onboard LED support for 96Boards Manivannan Sadhasivam
2018-10-29 9:42 ` [PATCH v3 1/7] arm64: dts: rockchip: ficus: Add on-board LED support Manivannan Sadhasivam
2018-12-11 19:11 ` Heiko Stuebner
2018-10-29 9:42 ` [PATCH v3 2/7] arm64: dts: rockchip: rock960: " Manivannan Sadhasivam
2018-12-11 19:11 ` Heiko Stuebner
2018-10-29 9:42 ` [PATCH v3 3/7] arm64: dts: hisilicon: hikey: Standardize LED labels and triggers Manivannan Sadhasivam
2018-10-29 9:42 ` [PATCH v3 4/7] arm64: dts: hisilicon: hikey960: " Manivannan Sadhasivam
2018-10-29 9:42 ` [PATCH v3 5/7] arm64: dts: hisilicon: poplar: " Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam [this message]
2018-12-21 2:37 ` [PATCH v3 6/7] arm64: dts: xilinx: ultra96: " Manivannan Sadhasivam
2018-12-21 6:50 ` Michal Simek
2019-01-24 16:49 ` Rob Herring
2019-01-29 13:17 ` Michal Simek
2018-10-29 9:42 ` [PATCH v3 7/7] arm64: dts: qcom: apq8016-sbc: Standardize LED labels Manivannan Sadhasivam
2018-12-21 2:35 ` Manivannan Sadhasivam
2019-02-05 19:00 ` Nicolas Dechesne
2019-02-05 19:24 ` Bjorn Andersson
2018-10-31 13:38 ` [PATCH v3 0/7] Standardize onboard LED support for 96Boards Linus Walleij
[not found] ` <CAHTX3dJTXtuA0i-ffPjoiWuxEcF_5JY55VJtWd9zxW4HxK1K3w@mail.gmail.com>
2018-10-31 21:17 ` Linus Walleij
2018-11-01 10:49 ` Heiko Stübner
2018-11-29 15:42 ` Wei Xu
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=20181029094245.7886-7-manivannan.sadhasivam@linaro.org \
--to=manivannan.sadhasivam@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=andy.gross@linaro.org \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=koen.kooi@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-soc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=nicolas.dechesne@linaro.org \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=xuwei5@hisilicon.com \
/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).