xref: /openbmc/linux/drivers/leds/trigger/Kconfig (revision 023e4163)
1menuconfig LEDS_TRIGGERS
2	bool "LED Trigger support"
3	depends on LEDS_CLASS
4	help
5	  This option enables trigger support for the leds class.
6	  These triggers allow kernel events to drive the LEDs and can
7	  be configured via sysfs. If unsure, say Y.
8
9if LEDS_TRIGGERS
10
11config LEDS_TRIGGER_TIMER
12	tristate "LED Timer Trigger"
13	help
14	  This allows LEDs to be controlled by a programmable timer
15	  via sysfs. Some LED hardware can be programmed to start
16	  blinking the LED without any further software interaction.
17	  For more details read Documentation/leds/leds-class.txt.
18
19	  If unsure, say Y.
20
21config LEDS_TRIGGER_ONESHOT
22	tristate "LED One-shot Trigger"
23	help
24	  This allows LEDs to blink in one-shot pulses with parameters
25	  controlled via sysfs.  It's useful to notify the user on
26	  sporadic events, when there are no clear begin and end trap points,
27	  or on dense events, where this blinks the LED at constant rate if
28	  rearmed continuously.
29
30	  It also shows how to use the led_blink_set_oneshot() function.
31
32	  If unsure, say Y.
33
34config LEDS_TRIGGER_DISK
35	bool "LED Disk Trigger"
36	depends on IDE_GD_ATA || ATA
37	help
38	  This allows LEDs to be controlled by disk activity.
39	  If unsure, say Y.
40
41config LEDS_TRIGGER_MTD
42	bool "LED MTD (NAND/NOR) Trigger"
43	depends on MTD
44	help
45	  This allows LEDs to be controlled by MTD activity.
46	  If unsure, say N.
47
48config LEDS_TRIGGER_HEARTBEAT
49	tristate "LED Heartbeat Trigger"
50	help
51	  This allows LEDs to be controlled by a CPU load average.
52	  The flash frequency is a hyperbolic function of the 1-minute
53	  load average.
54	  If unsure, say Y.
55
56config LEDS_TRIGGER_BACKLIGHT
57	tristate "LED backlight Trigger"
58	help
59	  This allows LEDs to be controlled as a backlight device: they
60	  turn off and on when the display is blanked and unblanked.
61
62	  If unsure, say N.
63
64config LEDS_TRIGGER_CPU
65	bool "LED CPU Trigger"
66	help
67	  This allows LEDs to be controlled by active CPUs. This shows
68	  the active CPUs across an array of LEDs so you can see which
69	  CPUs are active on the system at any given moment.
70
71	  If unsure, say N.
72
73config LEDS_TRIGGER_ACTIVITY
74	tristate "LED activity Trigger"
75	help
76	  This allows LEDs to be controlled by an immediate CPU usage.
77	  The flash frequency and duty cycle varies from faint flashes to
78	  intense brightness depending on the instant CPU load.
79	  If unsure, say N.
80
81config LEDS_TRIGGER_GPIO
82	tristate "LED GPIO Trigger"
83	depends on GPIOLIB || COMPILE_TEST
84	help
85	  This allows LEDs to be controlled by gpio events. It's good
86	  when using gpios as switches and triggering the needed LEDs
87	  from there. One use case is n810's keypad LEDs that could
88	  be triggered by this trigger when user slides up to show
89	  keypad.
90
91	  If unsure, say N.
92
93config LEDS_TRIGGER_DEFAULT_ON
94	tristate "LED Default ON Trigger"
95	help
96	  This allows LEDs to be initialised in the ON state.
97	  If unsure, say Y.
98
99comment "iptables trigger is under Netfilter config (LED target)"
100	depends on LEDS_TRIGGERS
101
102config LEDS_TRIGGER_TRANSIENT
103	tristate "LED Transient Trigger"
104	help
105	  This allows one time activation of a transient state on
106	  GPIO/PWM based hardware.
107	  If unsure, say Y.
108
109config LEDS_TRIGGER_CAMERA
110	tristate "LED Camera Flash/Torch Trigger"
111	help
112	  This allows LEDs to be controlled as a camera flash/torch device.
113	  This enables direct flash/torch on/off by the driver, kernel space.
114	  If unsure, say Y.
115
116config LEDS_TRIGGER_PANIC
117	bool "LED Panic Trigger"
118	help
119	  This allows LEDs to be configured to blink on a kernel panic.
120	  Enabling this option will allow to mark certain LEDs as panic indicators,
121	  allowing to blink them on a kernel panic, even if they are set to
122	  a different trigger.
123	  If unsure, say Y.
124
125config LEDS_TRIGGER_NETDEV
126	tristate "LED Netdev Trigger"
127	depends on NET
128	help
129	  This allows LEDs to be controlled by network device activity.
130	  If unsure, say Y.
131
132config LEDS_TRIGGER_PATTERN
133	tristate "LED Pattern Trigger"
134	help
135	  This allows LEDs to be controlled by a software or hardware pattern
136	  which is a series of tuples, of brightness and duration (ms).
137	  If unsure, say N
138
139config LEDS_TRIGGER_AUDIO
140	tristate "Audio Mute LED Trigger"
141	help
142	  This allows LEDs to be controlled by audio drivers for following
143	  the audio mute and mic-mute changes.
144	  If unsure, say N
145
146endif # LEDS_TRIGGERS
147