summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarek BehĂșn <kabel@kernel.org>2020-10-19 13:08:08 +0200
committerPavel Machek <pavel@ucw.cz>2020-10-26 09:21:51 +0100
commit12ec7e56ce95d7b6fd4cd74e634c1181e2b424e1 (patch)
tree899957204355aac81ba4ada48442424722efb9a7
parentLinux 5.10-rc1 (diff)
downloadlinux-12ec7e56ce95d7b6fd4cd74e634c1181e2b424e1.tar.xz
linux-12ec7e56ce95d7b6fd4cd74e634c1181e2b424e1.zip
Documentation: leds: remove invalidated information
The contents of the Future Development section of leds-class Documentation was invalidated when support for LED-private triggers was merged. Remove this section. Signed-off-by: Marek BehĂșn <kabel@kernel.org> Fixes: 93690cdf3060 ("leds: trigger: add support for LED-private device...") Signed-off-by: Pavel Machek <pavel@ucw.cz>
-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.