diff options
| author | Rafał Miłecki <rafal@milecki.pl> | 2023-03-16 16:55:46 +0300 |
|---|---|---|
| committer | Lee Jones <lee@kernel.org> | 2023-03-16 18:32:53 +0300 |
| commit | 820d7550a99cc09bb321fb2b890647e3669ce53f (patch) | |
| tree | 50973619d3e0191b0c98cd55ab6b7ef81ef2bdfd /Documentation/devicetree/bindings/leds | |
| parent | 1aeff621689120db60cb7029e5a0fde7d01f7fb6 (diff) | |
| download | linux-820d7550a99cc09bb321fb2b890647e3669ce53f.tar.xz | |
dt-bindings: leds: Add "usbport" trigger
Linux's "usbport" trigger is a bit specific one. It allows LED to follow
state of multiple USB ports which have to be selected additionally
(there isn't a single trigger for each port).
Default list of USB ports to monitor can be specified using
"trigger-sources" DT property. Theoretically it should be possible for
Linux to deduce applicable trigger based on the references nodes in the
"trigger-sources". It hasn't been implemented however (probably due to
laziness).
Milk spilled - we already have DT files specifying "usbport" manually -
allow that value in the binding. This fixes validation of in-kernel and
external DT files.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Signed-off-by: Lee Jones <lee@kernel.org>
Link: https://lore.kernel.org/r/20230316135546.9162-1-zajec5@gmail.com
Diffstat (limited to 'Documentation/devicetree/bindings/leds')
| -rw-r--r-- | Documentation/devicetree/bindings/leds/common.yaml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml index 61e63ed81ced..11aedf1650a1 100644 --- a/Documentation/devicetree/bindings/leds/common.yaml +++ b/Documentation/devicetree/bindings/leds/common.yaml @@ -125,6 +125,8 @@ properties: - usb-gadget # LED indicates USB host activity - usb-host + # LED indicates USB port state + - usbport # LED is triggered by CPU activity - pattern: "^cpu[0-9]*$" # LED is triggered by Bluetooth activity |