Orange Pi5 kernel

Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards

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