On Wed, 10 Dec 2014 02:02:14 +0100 Samuel Thibault <[email protected]> wrote:
> This permits to reassign keyboard LEDs to something else than keyboard "leds" > state, by adding keyboard led and modifier triggers connected to a series > of VT input LEDs, themselves connected to VT input triggers, which > per-input device LEDs use by default. Userland can thus easily change the LED > behavior of (a priori) all input devices, or of particular input devices. > > This also permits to fix #7063 from userland by using a modifier to implement > proper CapsLock behavior and have the keyboard caps lock led show that > modifier > state. > > [[email protected]: Rebased to 3.2-rc1 or so, cleaned up some includes, > and fixed some constants] > [[email protected]: CONFIG_INPUT_LEDS stubs should be static inline] > [[email protected]: remove unneeded `extern', fix comment layout] > Signed-off-by: Samuel Thibault <[email protected]> > Signed-off-by: Evan Broder <[email protected]> > Reviewed-by: David Herrmann <[email protected]> > Tested-by: Pavel Machek <[email protected]> > Acked-by: Peter Korsgaard <[email protected]> > Signed-off-by: John Crispin <[email protected]> > Signed-off-by: Andrew Morton <[email protected]> > --- > Changed in this version: > - Use kcalloc instead of kzalloc > - to avoid any mutex order violation, defer LED update into a work callback. Confused. This patch is identical to the one that's presently in -mm. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
