Subject: [PATCHv6 2/2] INPUT: Introduce generic trigger/LED pairs to input LEDs

From: [email-masked] (Dmitry Torokhov)
Date: Tue, 10 Feb 2015 14:11:05 -0800

Hi Samuel,

On Fri, Jan 23, 2015 at 01:28:14PM +0100, Samuel Thibault wrote:
> This permits to reassign input LEDs to something else than keyboard "leds"
> state, by adding a trigger and a led for each input leds, the former being
> triggered by EV_LED events, and the latter being by default triggered by the
> former. The user can then make the LED use another trigger, including other LED
> triggers of the same keyboard.
> 
> The hardware LEDs are now not actioned from the EV_LED event any more, but from
> the per-device LED layer.
> 
> [ebroder at mokafive.com: Rebased to 3.2-rc1 or so, cleaned up some includes, and fixed some constants]
> [akpm at linux-foundation.org: remove unneeded `extern', fix comment layout]
> Signed-off-by: Samuel Thibault <[email-masked]>
> Signed-off-by: Evan Broder <[email-masked]>
> Acked-by: Peter Korsgaard <[email-masked]>
> Signed-off-by: John Crispin <[email-masked]>
> Signed-off-by: Andrew Morton <[email-masked]>
> ---
> Changed in this version:
> - use drvdata instead of platform_data
> - dropped CONFIG_INPUT_LEDS option
> - compacted leds and triggers array allocation
> - handle registration failure

This did not make the first batch, but I will try to get it into the
2nd.

Pavel, have you tried this version?

Thanks!
 
-- 
Dmitry