Lines Matching refs:LED
2 LED handling under Linux
5 In its simplest form, the LED class just allows control of LEDs from
7 LED is defined in max_brightness file. The brightness file will set the brightness
8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
11 The class also introduces the optional concept of an LED trigger. A trigger
18 Complex triggers while available to all LEDs have LED specific
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
23 You can change the brightness value of a LED independently of the timer
41 LED Device Naming
68 It is possible that more than one LED with the same color and function will
73 automatically by the LED core upon LED class device registration.
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
78 suffix (e.g. "_1", "_2", "_3" etc.) is added to the requested LED class
81 There might be still LED class drivers around using vendor or product name
86 Examples of proper LED names:
101 get_led_device_info.sh script can be used for verifying if the LED name
102 meets the requirements pointed out here. It performs validation of the LED class
112 There have been calls for LED properties such as color to be exported as
122 LED subsystem core exposes following API for setting brightness:
135 LED registration API
138 A driver wanting to register a LED classdev for use by other drivers /
154 support this feature, a LED driver can optionally implement the
155 blink_set() function (see <linux/leds.h>). To set an LED to blinking,
169 should completely turn off the LED and cancel the previously programmed
176 The LED Trigger core cannot be a module as the simple trigger functions
179 rest of the LED subsystem can be modular.