summaryrefslogtreecommitdiffstats
path: root/drivers/leds/Kconfig
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2015-03-16 21:19:56 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2015-06-11 18:18:11 -0700
commitf60c8ba77dcea80af8facfd786a0d2c3ace86f3d (patch)
tree4dc115384ea35ba027b7514ca5e6f5fd388daf61 /drivers/leds/Kconfig
parentcf99289d67688c4f92175da42bd1647695f6fddc (diff)
downloadop-kernel-dev-f60c8ba77dcea80af8facfd786a0d2c3ace86f3d.zip
op-kernel-dev-f60c8ba77dcea80af8facfd786a0d2c3ace86f3d.tar.gz
Input: export LEDs as class devices in sysfs
This change creates a new input handler called "leds" that exports LEDs on input devices as standard LED class devices in sysfs and allows controlling their state via sysfs or via any of the standard LED triggers. This allows to re-purpose and reassign LDEs on the keyboards to represent states other than the standard keyboard states (CapsLock, NumLock, etc). The old API of controlling input LEDs by writing into /dev/input/eventX devices is still present and will take precedence over accessing via LEDs subsystem (i.e. it may override state set by a trigger). If input device is "grabbed" then requests coming through LED subsystem will be ignored. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> Tested-by: Pavel Machek <pavel@ucw.cz> Acked-by: Pavel Machek <pavel@ucw.cz> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/leds/Kconfig')
-rw-r--r--drivers/leds/Kconfig3
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index 25b320d..95029df 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -11,9 +11,6 @@ menuconfig NEW_LEDS
Say Y to enable Linux LED support. This allows control of supported
LEDs from both userspace and optionally, by kernel events (triggers).
- This is not related to standard keyboard LEDs which are controlled
- via the input system.
-
if NEW_LEDS
config LEDS_CLASS
OpenPOWER on IntegriCloud