mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-21 15:42:49 +07:00
7df4f9a9f0
The "activity" trigger was inspired by the heartbeat one, but aims at providing instant indication of the immediate CPU usage. Under idle condition, it flashes 10ms every second. At 100% usage, it flashes 90ms every 100ms. The blinking frequency increases from 1 to 10 Hz until either the load is high enough to saturate one CPU core or 50% load is reached on a single-core system. Then past this point only the duty cycle increases from 10 to 90%. This results in a very visible activity reporting allowing one to immediately tell whether a machine is under load or not, making it quite suitable to be used in clusters. Signed-off-by: Willy Tarreau <w@1wt.eu> Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
139 lines
4.0 KiB
Plaintext
139 lines
4.0 KiB
Plaintext
menuconfig LEDS_TRIGGERS
|
|
bool "LED Trigger support"
|
|
depends on LEDS_CLASS
|
|
help
|
|
This option enables trigger support for the leds class.
|
|
These triggers allow kernel events to drive the LEDs and can
|
|
be configured via sysfs. If unsure, say Y.
|
|
|
|
if LEDS_TRIGGERS
|
|
|
|
config LEDS_TRIGGER_TIMER
|
|
tristate "LED Timer Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be controlled by a programmable timer
|
|
via sysfs. Some LED hardware can be programmed to start
|
|
blinking the LED without any further software interaction.
|
|
For more details read Documentation/leds/leds-class.txt.
|
|
|
|
If unsure, say Y.
|
|
|
|
config LEDS_TRIGGER_ONESHOT
|
|
tristate "LED One-shot Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to blink in one-shot pulses with parameters
|
|
controlled via sysfs. It's useful to notify the user on
|
|
sporadic events, when there are no clear begin and end trap points,
|
|
or on dense events, where this blinks the LED at constant rate if
|
|
rearmed continuously.
|
|
|
|
It also shows how to use the led_blink_set_oneshot() function.
|
|
|
|
If unsure, say Y.
|
|
|
|
config LEDS_TRIGGER_DISK
|
|
bool "LED Disk Trigger"
|
|
depends on IDE_GD_ATA || ATA
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be controlled by disk activity.
|
|
If unsure, say Y.
|
|
|
|
config LEDS_TRIGGER_MTD
|
|
bool "LED MTD (NAND/NOR) Trigger"
|
|
depends on MTD
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be controlled by MTD activity.
|
|
If unsure, say N.
|
|
|
|
config LEDS_TRIGGER_HEARTBEAT
|
|
tristate "LED Heartbeat Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be controlled by a CPU load average.
|
|
The flash frequency is a hyperbolic function of the 1-minute
|
|
load average.
|
|
If unsure, say Y.
|
|
|
|
config LEDS_TRIGGER_BACKLIGHT
|
|
tristate "LED backlight Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be controlled as a backlight device: they
|
|
turn off and on when the display is blanked and unblanked.
|
|
|
|
If unsure, say N.
|
|
|
|
config LEDS_TRIGGER_CPU
|
|
bool "LED CPU Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be controlled by active CPUs. This shows
|
|
the active CPUs across an array of LEDs so you can see which
|
|
CPUs are active on the system at any given moment.
|
|
|
|
If unsure, say N.
|
|
|
|
config LEDS_TRIGGER_ACTIVITY
|
|
tristate "LED activity Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be controlled by a immediate CPU usage.
|
|
The flash frequency and duty cycle varies from faint flashes to
|
|
intense brightness depending on the instant CPU load.
|
|
If unsure, say N.
|
|
|
|
config LEDS_TRIGGER_GPIO
|
|
tristate "LED GPIO Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
depends on GPIOLIB || COMPILE_TEST
|
|
help
|
|
This allows LEDs to be controlled by gpio events. It's good
|
|
when using gpios as switches and triggering the needed LEDs
|
|
from there. One use case is n810's keypad LEDs that could
|
|
be triggered by this trigger when user slides up to show
|
|
keypad.
|
|
|
|
If unsure, say N.
|
|
|
|
config LEDS_TRIGGER_DEFAULT_ON
|
|
tristate "LED Default ON Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be initialised in the ON state.
|
|
If unsure, say Y.
|
|
|
|
comment "iptables trigger is under Netfilter config (LED target)"
|
|
depends on LEDS_TRIGGERS
|
|
|
|
config LEDS_TRIGGER_TRANSIENT
|
|
tristate "LED Transient Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows one time activation of a transient state on
|
|
GPIO/PWM based hardware.
|
|
If unsure, say Y.
|
|
|
|
config LEDS_TRIGGER_CAMERA
|
|
tristate "LED Camera Flash/Torch Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be controlled as a camera flash/torch device.
|
|
This enables direct flash/torch on/off by the driver, kernel space.
|
|
If unsure, say Y.
|
|
|
|
config LEDS_TRIGGER_PANIC
|
|
bool "LED Panic Trigger"
|
|
depends on LEDS_TRIGGERS
|
|
help
|
|
This allows LEDs to be configured to blink on a kernel panic.
|
|
Enabling this option will allow to mark certain LEDs as panic indicators,
|
|
allowing to blink them on a kernel panic, even if they are set to
|
|
a different trigger.
|
|
If unsure, say Y.
|
|
|
|
endif # LEDS_TRIGGERS
|