~hc/RK356X_SDK_RELEASE.git

..	..	@@ -1,3 +1,4 @@
	1	+# SPDX-License-Identifier: GPL-2.0-only
1	2	menuconfig LEDS_TRIGGERS
2	3	bool "LED Trigger support"
3	4	depends on LEDS_CLASS
..	..	@@ -14,7 +15,7 @@
14	15	This allows LEDs to be controlled by a programmable timer
15	16	via sysfs. Some LED hardware can be programmed to start
16	17	blinking the LED without any further software interaction.
17		- For more details read Documentation/leds/leds-class.txt.
	18	+ For more details read Documentation/leds/leds-class.rst.
18	19
19	20	If unsure, say Y.
20	21
..	..	@@ -63,7 +64,6 @@
63	64
64	65	config LEDS_TRIGGER_CPU
65	66	bool "LED CPU Trigger"
66		- depends on !PREEMPT_RT_BASE
67	67	help
68	68	This allows LEDs to be controlled by active CPUs. This shows
69	69	the active CPUs across an array of LEDs so you can see which
..	..	@@ -130,4 +130,18 @@
130	130	This allows LEDs to be controlled by network device activity.
131	131	If unsure, say Y.
132	132
	133	+config LEDS_TRIGGER_PATTERN
	134	+ tristate "LED Pattern Trigger"
	135	+ help
	136	+ This allows LEDs to be controlled by a software or hardware pattern
	137	+ which is a series of tuples, of brightness and duration (ms).
	138	+ If unsure, say N
	139	+
	140	+config LEDS_TRIGGER_AUDIO
	141	+ tristate "Audio Mute LED Trigger"
	142	+ help
	143	+ This allows LEDs to be controlled by audio drivers for following
	144	+ the audio mute and mic-mute changes.
	145	+ If unsure, say N
	146	+
133	147	endif # LEDS_TRIGGERS