aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/leds
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-12-16 14:56:29 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2020-12-16 14:56:29 -0800
commit945433be3677955255fabecbf1076c17864ff9da (patch)
tree1141cc791dc2daa59516a83cca3d4e54a6a81977 /Documentation/leds
parentMerge tag 'for-linus-5.11-1' of git://github.com/cminyard/linux-ipmi (diff)
parentleds: turris-omnia: check for LED_COLOR_ID_RGB instead LED_COLOR_ID_MULTI (diff)
downloadlinux-dev-945433be3677955255fabecbf1076c17864ff9da.tar.xz
linux-dev-945433be3677955255fabecbf1076c17864ff9da.zip
Merge tag 'leds-5.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds
Pull LED updates from Pavel Machek: "Small cleanups/fixes mostly thanks to Marek, nothing major made it in this time" * tag 'leds-5.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds: leds: turris-omnia: check for LED_COLOR_ID_RGB instead LED_COLOR_ID_MULTI leds: turris-omnia: fix checkpatch warning leds: turris-omnia: wrap to 80 columns leds: turris-omnia: use constants instead of macros for color command dt-bindings: leds: Convert pwm to yaml leds: lp50xx: Fix an error handling path in 'lp50xx_probe_dt()' leds: netxbig: add missing put_device() call in netxbig_leds_get_of_pdata() Documentation: leds: remove invalidated information
Diffstat (limited to 'Documentation/leds')
-rw-r--r--Documentation/leds/leds-class.rst10
1 files changed, 0 insertions, 10 deletions
diff --git a/Documentation/leds/leds-class.rst b/Documentation/leds/leds-class.rst
index a0708d3f3d0b..cd155ead8703 100644
--- a/Documentation/leds/leds-class.rst
+++ b/Documentation/leds/leds-class.rst
@@ -177,13 +177,3 @@ The LED Trigger core cannot be a module as the simple trigger functions
would cause nightmare dependency issues. I see this as a minor issue
compared to the benefits the simple trigger functionality brings. The
rest of the LED subsystem can be modular.
-
-
-Future Development
-==================
-
-At the moment, a trigger can't be created specifically for a single LED.
-There are a number of cases where a trigger might only be mappable to a
-particular LED (ACPI?). The addition of triggers provided by the LED driver
-should cover this option and be possible to add without breaking the
-current interface.