Lines Matching +full:software +full:- +full:initiated

8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
9 brightness support so will just be turned on for non-zero brightness settings.
14 existing subsystems with minimal additional code. Examples are the disk-activity,
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
48 - devicename:
57 - color:
59         include/dt-bindings/leds/common.h.
61 - function:
63         include/dt-bindings/leds/common.h.
66 to linux-leds@vger.kernel.org.
71 name with required "-N" suffix in the driver. fwnode based drivers can use
72 function-enumerator property for that and then the concatenation will be handled
76 when LED class device is created by a driver of hot-pluggable device and
88   - "red:disk"
89   - "white:flash"
90   - "red:indicator"
91   - "phy1:green:wlan"
92   - "phy3::wlan"
93   - ":kbd_backlight"
94   - "input5::kbd_backlight"
95   - "input3::numlock"
96   - "input3::scrolllock"
97   - "input3::capslock"
98   - "mmc1::status"
99   - "white:status"
107         - input devices
108         - ieee80211 compliant USB devices
124     - led_set_brightness:
128     - led_set_brightness_sync:
129 		for use cases when immediate effect is desired -
132 		blinking, returns -EBUSY if software blink fallback is enabled.
142 free-ing the led_classdev struct.
144 If the driver can detect hardware initiated brightness changes and thus
157 will check and implement software fallback if necessary.
160 with brightness value LED_OFF, which should stop any software
184     - hw_control_trigger:
189     - hw_control_is_supported:
196                 If the passed flags mask is not supported -EOPNOTSUPP
197                 must be returned, the LED trigger will use software
203      - hw_control_set:
214     - hw_control_get:
225     - hw_control_get_device:
251 When the LED is in hw control, no software blink is possible and doing so