[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210923065500.2284347-4-daniel@0x0f.com>
Date: Thu, 23 Sep 2021 15:54:52 +0900
From: Daniel Palmer <daniel@...f.com>
To: devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-leds@...r.kernel.org
Cc: linus.walleij@...aro.org, bgolaszewski@...libre.com,
robh+dt@...nel.org, pavel@....cz,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Daniel Palmer <daniel@...f.com>
Subject: [PATCH v2 03/11] dt-bindings: leds: Document "activity" trigger
The "activity" trigger can be used as the default but it's currently
undocumented so validating a devicetree that uses it causes a warning.
Signed-off-by: Daniel Palmer <daniel@...f.com>
---
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 697102707703..8160a5073728 100644
--- a/Documentation/devicetree/bindings/leds/common.yaml
+++ b/Documentation/devicetree/bindings/leds/common.yaml
@@ -80,6 +80,8 @@ properties:
$ref: /schemas/types.yaml#/definitions/string
enum:
+ # LED will flashing will represent current CPU usage
+ - activity
# LED will act as a back-light, controlled by the framebuffer system
- backlight
# LED will turn on (but for leds-gpio see "default-state" property in
--
2.33.0
Powered by blists - more mailing lists