1 # SPDX-License-Identifier: GPL-2.0-only
2 menuconfig LEDS_TRIGGERS
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
8 be configured via sysfs. If unsure, say Y.
12 config LEDS_TRIGGER_TIMER
13 tristate "LED Timer Trigger"
15 This allows LEDs to be controlled by a programmable timer
16 via sysfs. Some LED hardware can be programmed to start
17 blinking the LED without any further software interaction.
18 For more details read Documentation/leds/leds-class.rst.
22 config LEDS_TRIGGER_ONESHOT
23 tristate "LED One-shot Trigger"
25 This allows LEDs to blink in one-shot pulses with parameters
26 controlled via sysfs. It's useful to notify the user on
27 sporadic events, when there are no clear begin and end trap points,
28 or on dense events, where this blinks the LED at constant rate if
31 It also shows how to use the led_blink_set_oneshot() function.
35 config LEDS_TRIGGER_DISK
36 bool "LED Disk Trigger"
39 This allows LEDs to be controlled by disk activity.
42 config LEDS_TRIGGER_MTD
43 bool "LED MTD (NAND/NOR) Trigger"
46 This allows LEDs to be controlled by MTD activity.
49 config LEDS_TRIGGER_HEARTBEAT
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
57 config LEDS_TRIGGER_BACKLIGHT
58 tristate "LED backlight Trigger"
60 This allows LEDs to be controlled as a backlight device: they
61 turn off and on when the display is blanked and unblanked.
65 config LEDS_TRIGGER_CPU
66 bool "LED CPU Trigger"
68 This allows LEDs to be controlled by active CPUs. This shows
69 the active CPUs across an array of LEDs so you can see which
70 CPUs are active on the system at any given moment.
74 config LEDS_TRIGGER_ACTIVITY
75 tristate "LED activity Trigger"
77 This allows LEDs to be controlled by an immediate CPU usage.
78 The flash frequency and duty cycle varies from faint flashes to
79 intense brightness depending on the instant CPU load.
82 config LEDS_TRIGGER_GPIO
83 tristate "LED GPIO Trigger"
84 depends on GPIOLIB || COMPILE_TEST
86 This allows LEDs to be controlled by gpio events. It's good
87 when using gpios as switches and triggering the needed LEDs
88 from there. One use case is n810's keypad LEDs that could
89 be triggered by this trigger when user slides up to show
94 config LEDS_TRIGGER_DEFAULT_ON
95 tristate "LED Default ON Trigger"
97 This allows LEDs to be initialised in the ON state.
100 comment "iptables trigger is under Netfilter config (LED target)"
101 depends on LEDS_TRIGGERS
103 config LEDS_TRIGGER_TRANSIENT
104 tristate "LED Transient Trigger"
106 This allows one time activation of a transient state on
107 GPIO/PWM based hardware.
110 config LEDS_TRIGGER_CAMERA
111 tristate "LED Camera Flash/Torch Trigger"
113 This allows LEDs to be controlled as a camera flash/torch device.
114 This enables direct flash/torch on/off by the driver, kernel space.
117 config LEDS_TRIGGER_INPUT
118 tristate "LED Input Trigger"
119 depends on LEDS_TRIGGERS
121 This allows the GPIOs assigned to be LEDs to be initialised to inputs.
124 config LEDS_TRIGGER_PANIC
125 bool "LED Panic Trigger"
127 This allows LEDs to be configured to blink on a kernel panic.
128 Enabling this option will allow to mark certain LEDs as panic indicators,
129 allowing to blink them on a kernel panic, even if they are set to
133 config LEDS_TRIGGER_NETDEV
134 tristate "LED Netdev Trigger"
137 This allows LEDs to be controlled by network device activity.
140 config LEDS_TRIGGER_PATTERN
141 tristate "LED Pattern Trigger"
143 This allows LEDs to be controlled by a software or hardware pattern
144 which is a series of tuples, of brightness and duration (ms).
147 config LEDS_TRIGGER_AUDIO
148 tristate "Audio Mute LED Trigger"
150 This allows LEDs to be controlled by audio drivers for following
151 the audio mute and mic-mute changes.
154 config LEDS_TRIGGER_TTY
155 tristate "LED Trigger for TTY devices"
158 This allows LEDs to be controlled by activity on ttys which includes
159 serial devices like /dev/ttyS0.
161 When build as a module this driver will be called ledtrig-tty.
163 config LEDS_TRIGGER_ACTPWR
164 tristate "ACT/PWR Input Trigger"
165 depends on LEDS_TRIGGERS
167 This trigger is intended for platforms that have one software-
168 controllable LED and no dedicated activity or power LEDs, hence the
169 need to make the one LED perform both functions. It cycles between
170 default-on and an inverted mmc0 every 500ms, guaranteeing that it is
171 on for at least half of the time.
174 endif # LEDS_TRIGGERS