0001 # SPDX-License-Identifier: GPL-2.0-only
0002 menuconfig LEDS_TRIGGERS
0003 bool "LED Trigger support"
0004 depends on LEDS_CLASS
0005 help
0006 This option enables trigger support for the leds class.
0007 These triggers allow kernel events to drive the LEDs and can
0008 be configured via sysfs. If unsure, say Y.
0009
0010 if LEDS_TRIGGERS
0011
0012 config LEDS_TRIGGER_TIMER
0013 tristate "LED Timer Trigger"
0014 help
0015 This allows LEDs to be controlled by a programmable timer
0016 via sysfs. Some LED hardware can be programmed to start
0017 blinking the LED without any further software interaction.
0018 For more details read Documentation/leds/leds-class.rst.
0019
0020 If unsure, say Y.
0021
0022 config LEDS_TRIGGER_ONESHOT
0023 tristate "LED One-shot Trigger"
0024 help
0025 This allows LEDs to blink in one-shot pulses with parameters
0026 controlled via sysfs. It's useful to notify the user on
0027 sporadic events, when there are no clear begin and end trap points,
0028 or on dense events, where this blinks the LED at constant rate if
0029 rearmed continuously.
0030
0031 It also shows how to use the led_blink_set_oneshot() function.
0032
0033 If unsure, say Y.
0034
0035 config LEDS_TRIGGER_DISK
0036 bool "LED Disk Trigger"
0037 depends on ATA
0038 help
0039 This allows LEDs to be controlled by disk activity.
0040 If unsure, say Y.
0041
0042 config LEDS_TRIGGER_MTD
0043 bool "LED MTD (NAND/NOR) Trigger"
0044 depends on MTD
0045 help
0046 This allows LEDs to be controlled by MTD activity.
0047 If unsure, say N.
0048
0049 config LEDS_TRIGGER_HEARTBEAT
0050 tristate "LED Heartbeat Trigger"
0051 help
0052 This allows LEDs to be controlled by a CPU load average.
0053 The flash frequency is a hyperbolic function of the 1-minute
0054 load average.
0055 If unsure, say Y.
0056
0057 config LEDS_TRIGGER_BACKLIGHT
0058 tristate "LED backlight Trigger"
0059 help
0060 This allows LEDs to be controlled as a backlight device: they
0061 turn off and on when the display is blanked and unblanked.
0062
0063 If unsure, say N.
0064
0065 config LEDS_TRIGGER_CPU
0066 bool "LED CPU Trigger"
0067 depends on !PREEMPT_RT
0068 help
0069 This allows LEDs to be controlled by active CPUs. This shows
0070 the active CPUs across an array of LEDs so you can see which
0071 CPUs are active on the system at any given moment.
0072
0073 If unsure, say N.
0074
0075 config LEDS_TRIGGER_ACTIVITY
0076 tristate "LED activity Trigger"
0077 help
0078 This allows LEDs to be controlled by an immediate CPU usage.
0079 The flash frequency and duty cycle varies from faint flashes to
0080 intense brightness depending on the instant CPU load.
0081 If unsure, say N.
0082
0083 config LEDS_TRIGGER_GPIO
0084 tristate "LED GPIO Trigger"
0085 depends on GPIOLIB || COMPILE_TEST
0086 help
0087 This allows LEDs to be controlled by gpio events. It's good
0088 when using gpios as switches and triggering the needed LEDs
0089 from there. One use case is n810's keypad LEDs that could
0090 be triggered by this trigger when user slides up to show
0091 keypad.
0092
0093 If unsure, say N.
0094
0095 config LEDS_TRIGGER_DEFAULT_ON
0096 tristate "LED Default ON Trigger"
0097 help
0098 This allows LEDs to be initialised in the ON state.
0099 If unsure, say Y.
0100
0101 comment "iptables trigger is under Netfilter config (LED target)"
0102 depends on LEDS_TRIGGERS
0103
0104 config LEDS_TRIGGER_TRANSIENT
0105 tristate "LED Transient Trigger"
0106 help
0107 This allows one time activation of a transient state on
0108 GPIO/PWM based hardware.
0109 If unsure, say Y.
0110
0111 config LEDS_TRIGGER_CAMERA
0112 tristate "LED Camera Flash/Torch Trigger"
0113 help
0114 This allows LEDs to be controlled as a camera flash/torch device.
0115 This enables direct flash/torch on/off by the driver, kernel space.
0116 If unsure, say Y.
0117
0118 config LEDS_TRIGGER_PANIC
0119 bool "LED Panic Trigger"
0120 help
0121 This allows LEDs to be configured to blink on a kernel panic.
0122 Enabling this option will allow to mark certain LEDs as panic indicators,
0123 allowing to blink them on a kernel panic, even if they are set to
0124 a different trigger.
0125 If unsure, say Y.
0126
0127 config LEDS_TRIGGER_NETDEV
0128 tristate "LED Netdev Trigger"
0129 depends on NET
0130 help
0131 This allows LEDs to be controlled by network device activity.
0132 If unsure, say Y.
0133
0134 config LEDS_TRIGGER_PATTERN
0135 tristate "LED Pattern Trigger"
0136 help
0137 This allows LEDs to be controlled by a software or hardware pattern
0138 which is a series of tuples, of brightness and duration (ms).
0139 If unsure, say N
0140
0141 config LEDS_TRIGGER_AUDIO
0142 tristate "Audio Mute LED Trigger"
0143 help
0144 This allows LEDs to be controlled by audio drivers for following
0145 the audio mute and mic-mute changes.
0146 If unsure, say N
0147
0148 config LEDS_TRIGGER_TTY
0149 tristate "LED Trigger for TTY devices"
0150 depends on TTY
0151 help
0152 This allows LEDs to be controlled by activity on ttys which includes
0153 serial devices like /dev/ttyS0.
0154
0155 When build as a module this driver will be called ledtrig-tty.
0156
0157 endif # LEDS_TRIGGERS
