Lines Matching +full:trigger +full:- +full:name
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.
11 The class also introduces the optional concept of an LED trigger. A trigger
13 complex. A simple trigger isn't configurable and is designed to slot into
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
19 parameters and work on a per LED basis. The timer trigger is an example.
20 The timer trigger will periodically change the LED brightness between
24 trigger. However, if you set the brightness value to LED_OFF it will
25 also disable the timer trigger.
28 is chosen (via /sys/class/leds/<device>/trigger). Trigger specific
29 parameters can appear in /sys/class/leds/<device> once a given trigger is
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
75 LED subsystem has also a protection against name clash, that may occur
76 when LED class device is created by a driver of hot-pluggable device and
79 device name.
81 There might be still LED class drivers around using vendor or product name
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"
101 get_led_device_info.sh script can be used for verifying if the LED name
107 - input devices
108 - ieee80211 compliant USB devices
114 overhead, I suggest these become part of the device name. The naming scheme
116 of the name don't apply, just leave that section blank.
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.
148 the LED_BRIGHT_HW_CHANGED flag is a bug and will trigger a WARN_ON.
184 - hw_control_trigger:
185 unique trigger name supported by the LED in hw control
189 - hw_control_is_supported:
190 check if the flags passed by the supported trigger can
196 If the passed flags mask is not supported -EOPNOTSUPP
197 must be returned, the LED trigger will use software
203 - hw_control_set:
205 flags passed from the supported trigger, parse them to
214 - hw_control_get:
217 supported trigger.
223 trigger.
225 - hw_control_get_device:
227 hw control. A trigger might use this to match the
229 device for the trigger as the source for blinking
231 (example a netdev trigger configured to blink for a
239 impossibility of supporting each different mode on the supported trigger.
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,
248 A trigger can use hw_control_get to check if a LED is already in hw control
257 The LED Trigger core cannot be a module as the simple trigger functions
259 compared to the benefits the simple trigger functionality brings. The