From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: shawnguo@kernel.org, s.hauer@pengutronix.de, robh+dt@kernel.org
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
darshak.patel@einfochips.com, prajose.john@einfochips.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
linux-leds@vger.kernel.org
Subject: [PATCH v2 1/4] dt-bindings: leds: Document commonly used LED triggers
Date: Wed, 30 Oct 2019 14:31:21 +0530 [thread overview]
Message-ID: <20191030090124.24900-2-manivannan.sadhasivam@linaro.org> (raw)
In-Reply-To: <20191030090124.24900-1-manivannan.sadhasivam@linaro.org>
This commit documents the LED triggers used commonly in the SoCs. Not
all triggers are documented as some of them are very application specific.
Most of the triggers documented here are currently used in devicetrees
of many SoCs.
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>
Cc: Dan Murphy <dmurphy@ti.com>
Cc: linux-leds@vger.kernel.org
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
---
.../devicetree/bindings/leds/common.txt | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt
index 9fa6f9795d50..2a6806161590 100644
--- a/Documentation/devicetree/bindings/leds/common.txt
+++ b/Documentation/devicetree/bindings/leds/common.txt
@@ -55,6 +55,23 @@ Optional properties for child nodes:
"timer" - LED flashes at a fixed, configurable rate
"pattern" - LED alters the brightness for the specified duration with one
software timer (requires "led-pattern" property)
+ "mmc[N]" - LED indicates [N]th MMC storage activity
+ "flash" - LED indicates camera flash state
+ "torch" - LED indicates camera torch state
+ "audio-mute" - LED indicates audio mute state
+ "audio-micmute" - LED indicates mic mute state
+ "bluetooth-power" - LED indicates bluetooth power state
+ "usb-gadget" - LED indicates USB gadget activity
+ "usb-host" - LED indicates USB host activity
+ "mtd" - LED indicates MTD memory activity
+ "nand-disk" - LED indicates NAND memory activity (deprecated),
+ in new implementations use "mtd"
+ "disk-read" - LED indicates disk read activity
+ "disk-write" - LED indicates disk write activity
+ "none" - No trigger assigned to the LED. This is the default mode
+ if trigger is absent
+ "cpu" - LED indicates activity of all CPUs
+ "cpu[N]" - LED indicates activity of [N]th CPU
- led-pattern : Array of integers with default pattern for certain triggers.
Each trigger may parse this property differently:
--
2.17.1
next prev parent reply other threads:[~2019-10-30 9:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 9:01 [PATCH v2 0/4] Add support for Thor96 board Manivannan Sadhasivam
2019-10-30 9:01 ` Manivannan Sadhasivam [this message]
2019-11-05 22:04 ` [PATCH v2 1/4] dt-bindings: leds: Document commonly used LED triggers Rob Herring
2019-10-30 9:01 ` [PATCH v2 2/4] dt-bindings: arm: Add devicetree binding for Thor96 Board Manivannan Sadhasivam
2019-10-30 9:01 ` [PATCH v2 3/4] arm64: dts: freescale: Add devicetree support for Thor96 board Manivannan Sadhasivam
2019-10-30 9:01 ` [PATCH v2 4/4] mtd: spi-nor: Add support for w25q256jw Manivannan Sadhasivam
2019-11-01 13:48 ` Tudor.Ambarus
2019-11-01 14:58 ` Manivannan Sadhasivam
2019-11-01 15:55 ` Tudor.Ambarus
2019-11-01 16:09 ` Manivannan Sadhasivam
2019-11-07 12:30 ` Tudor.Ambarus
2019-11-07 12:40 ` Manivannan Sadhasivam
2019-11-11 19:31 ` Tudor.Ambarus
2020-01-09 3:33 ` [PATCH v2 0/4] Add support for Thor96 board Manivannan Sadhasivam
2020-01-09 6:39 ` Shawn Guo
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=20191030090124.24900-2-manivannan.sadhasivam@linaro.org \
--to=manivannan.sadhasivam@linaro.org \
--cc=darshak.patel@einfochips.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=festevam@gmail.com \
--cc=jacek.anaszewski@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=prajose.john@einfochips.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).