Lines Matching +full:leds +full:- +full:trigger +full:- +full:pattern

1 # SPDX-License-Identifier: GPL-2.0-only
3 	bool "LED Trigger support"
6 	  This option enables trigger support for the leds class.
7 	  These triggers allow kernel events to drive the LEDs and can
13 	tristate "LED Timer Trigger"
15 	  This allows LEDs to be controlled by a programmable timer
18 	  For more details read Documentation/leds/leds-class.rst.
23 	tristate "LED One-shot Trigger"
25 	  This allows LEDs to blink in one-shot pulses with parameters
36 	bool "LED Disk Trigger"
39 	  This allows LEDs to be controlled by disk activity.
43 	bool "LED MTD (NAND/NOR) Trigger"
46 	  This allows LEDs to be controlled by MTD activity.
50 	tristate "LED Heartbeat Trigger"
52 	  This allows LEDs to be controlled by a CPU load average.
53 	  The flash frequency is a hyperbolic function of the 1-minute
58 	tristate "LED backlight Trigger"
60 	  This allows LEDs to be controlled as a backlight device: they
66 	bool "LED CPU Trigger"
69 	  This allows LEDs to be controlled by active CPUs. This shows
70 	  the active CPUs across an array of LEDs so you can see which
76 	tristate "LED activity Trigger"
78 	  This allows LEDs to be controlled by an immediate CPU usage.
84 	tristate "LED GPIO Trigger"
88 	  This allows LEDs to be controlled by gpio events. It's good
89 	  when using gpios as switches and triggering the needed LEDs
90 	  from there. One use case is n810's keypad LEDs that could
91 	  be triggered by this trigger when user slides up to show
97 	tristate "LED Default ON Trigger"
99 	  This allows LEDs to be initialised in the ON state.
102 comment "iptables trigger is under Netfilter config (LED target)"
106 	tristate "LED Transient Trigger"
113 	tristate "LED Camera Flash/Torch Trigger"
115 	  This allows LEDs to be controlled as a camera flash/torch device.
120 	bool "LED Panic Trigger"
122 	  This allows LEDs to be configured to blink on a kernel panic.
123 	  Enabling this option will allow to mark certain LEDs as panic indicators,
125 	  a different trigger.
129 	tristate "LED Netdev Trigger"
132 	  This allows LEDs to be controlled by network device activity.
136 	tristate "LED Pattern Trigger"
138 	  This allows LEDs to be controlled by a software or hardware pattern
143 	tristate "Audio Mute LED Trigger"
145 	  This allows LEDs to be controlled by audio drivers for following
146 	  the audio mute and mic-mute changes.
150 	tristate "LED Trigger for TTY devices"
153 	  This allows LEDs to be controlled by activity on ttys which includes
156 	  When build as a module this driver will be called ledtrig-tty.