Thread (20 messages) 20 messages, 4 authors, 2022-10-02

Re: [PATCH v2 03/11] dt-bindings: leds: Document "activity" trigger

From: Rob Herring <robh@kernel.org>
Date: 2021-09-27 19:52:53
Also in: linux-devicetree, linux-gpio, linux-leds, lkml

On Thu, Sep 23, 2021 at 03:54:52PM +0900, Daniel Palmer wrote:
The "activity" trigger can be used as the default but it's currently
undocumented so validating a devicetree that uses it causes a warning.
It is preferred to use 'function' and LED_FUNCTION_CPU. Is there some 
reason that can't be used?
quoted hunk ↗ jump to hunk
Signed-off-by: Daniel Palmer <redacted>
---
 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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help