From: Marek Vasut <marex@denx.de>
To: linux-leds@vger.kernel.org
Cc: Marek Vasut <marex@denx.de>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: [PATCH 1/2] dt-bindings: leds: Document none trigger
Date: Sun, 24 Oct 2021 02:23:57 +0200 [thread overview]
Message-ID: <20211024002358.225750-1-marex@denx.de> (raw)
There is a trigger called "none" which triggers never, add it to the
list of valid trigger values.
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
To: linux-leds@vger.kernel.org
---
Documentation/devicetree/bindings/leds/common.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml
index 697102707703a..22197376fa3c7 100644
--- a/Documentation/devicetree/bindings/leds/common.yaml
+++ b/Documentation/devicetree/bindings/leds/common.yaml
@@ -92,6 +92,8 @@ properties:
# LED indicates IDE disk activity (deprecated), in new implementations
# use "disk-activity"
- ide-disk
+ # LED is not triggered
+ - none
# LED flashes at a fixed, configurable rate
- timer
# LED alters the brightness for the specified duration with one software
--
2.33.0
next reply other threads:[~2021-10-24 0:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 0:23 Marek Vasut [this message]
2021-10-24 0:23 ` [PATCH 2/2] dt-bindings: leds: Document mmc trigger Marek Vasut
2021-10-24 8:40 ` Pavel Machek
2021-10-24 18:03 ` Marek Vasut
2021-10-24 14:27 ` Rob Herring
2021-10-24 8:41 ` [PATCH 1/2] dt-bindings: leds: Document none trigger Pavel Machek
2021-10-24 18:05 ` Marek Vasut
2021-11-08 17:51 ` Rob Herring
2021-11-08 22:49 ` Marek Vasut
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=20211024002358.225750-1-marex@denx.de \
--to=marex@denx.de \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--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).