Lines Matching +full:use +full:- +full:leds

1 -*- org -*-
5 directories in /sys/class/leds. It would be nice if userland would
10 use one of the "good" names from this list, and you should extend the
14 wants to use particular feature, you should probe for good name, first,
17 Notice there's a list of functions in include/dt-bindings/leds/common.h .
21 Game controllers may feature LEDs to indicate a player number. This is commonly
23 The "player LEDs" are then programmed with a pattern to indicate a particular
24 player. For example, a game controller with 4 LEDs, may be programmed with "x---"
25 to indicate player 1, "-x--" to indicate player 2 etcetera where "x" means on.
26 Input drivers can utilize the LED class to expose the individual player LEDs
31 Good: "input*:*:player-{1,2,3,4,5}
38 Legacy: "shift-key-light" (Motorola Droid 4, capslock)
40 Set of common keyboard LEDs, going back to PC AT or so.
47 Legacy: "button-backlight" (Motorola Droid 4)
57 LEDs on notebook body, indicating that sound input / output is muted.
62 Legacy: "status-led:{red,green,blue}" (Motorola Droid 4)
65 Phones usually have multi-color status LED.
69 Good: "platform:*:charging" (allwinner sun50i, leds-cht-wcove)
83 * Ethernet LEDs
85 Currently two types of Network LEDs are support, those controlled by
90 Do not use the netdev name, such as eth0, enp1s0. These are not stable
93 ** MAC LEDs
96 Good: mdio_mux-0.1:00:green:left
101 multiple LEDs, use left/right, or top/bottom to indicate their
104 ** PHY LEDs
106 Good: f1072004.mdio-mii:00: white:WAN
107 Good: !mdio-mux!mdio@2!switch@0!mdio:01:green:right
108 Good: r8169-0-200:00:yellow:bottom