Lines Matching +full:hw +full:- +full:blink
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-[email protected].
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.
150 Hardware accelerated blink of LEDs
153 Some LEDs can be programmed to blink without any CPU interaction. To
176 limited to blink but also to turn off or on autonomously.
180 With hw control we refer to the LED driven by hardware.
182 LED driver must define the following value to support hw control:
184 - hw_control_trigger:
185 unique trigger name supported by the LED in hw control
188 LED driver must implement the following API to support hw control:
189 - hw_control_is_supported:
191 be parsed and activate hw control on the LED.
196 If the passed flags mask is not supported -EOPNOTSUPP
203 - hw_control_set:
204 activate hw control. LED driver will use the provided
209 Set LED_OFF via the brightness_set to deactivate hw control.
214 - hw_control_get:
215 get active modes from a LED already in hw control, parse
225 - hw_control_get_device:
227 hw control. A trigger might use this to match the
230 events and correctly enable hw control.
231 (example a netdev trigger configured to blink for a
233 to set hw control)
240 Examples are hardcoding the blink speed to a set interval, enable special
241 feature like bypassing blink if some requirements are not met.
243 A trigger should first check if the hw control API are supported by the LED
244 driver and check if the trigger is supported to verify if hw control is possible,
246 the end use hw_control_set to activate hw control.
248 A trigger can use hw_control_get to check if a LED is already in hw control
251 When the LED is in hw control, no software blink is possible and doing so
252 will effectively disable hw control.