linux/drivers/input/keyboard, branch v4.5

Input: adp5589 - fix row 5 handling for adp5589

2016-02-09T23:36:21Z

The adp5589 has row 5, don't skip it when creating the GPIO mapping. Otherwise the pin gets reserved as used and it is not possible to use it as a GPIO. Signed-off-by: Lars-Peter Clausen Acked-by: Michael Hennerich Signed-off-by: Dmitry Torokhov

Input: cap11xx - add missing of_node_put

2016-01-27T23:55:48Z

for_each_child_of_node performs an of_node_get on each iteration, so to break out of the loop an of_node_put is required. Found using Coccinelle. Signed-off-by: Amitoj Kaur Chawla Signed-off-by: Dmitry Torokhov

Input: gpio-keys - allow disabling individual buttons in DT

2016-01-13T08:18:06Z

Add support to disable buttons from DT via status property if given button is not supported on given platforms. This will help re-using existing dtsi files across multiple platforms. Signed-off-by: Laxman Dewangan Signed-off-by: Dmitry Torokhov

Input: gpio-keys - allow setting input device name in DT

2016-01-13T08:18:05Z

Allow specifying name if input device via device tree property. This helps userspace code to get name and perform proper event to key mapping in some cases (for example, on Android). Signed-off-by: Laxman Dewangan Signed-off-by: Dmitry Torokhov

Input: gpio-keys - fix check for disabling unsupported keys

2016-01-10T17:51:56Z

Commit 4ea14a53d8f881034fa9e186653821c4e3d9a8fb ("Input: gpio-keys - report error when disabling unsupported key") tried let user know that they attempted to disable an unsupported key, unfortunately the check is wrong as it believes that all codes are invalid. Fix it by ensuring that keys that we try to disable are subset of keys (or switches) that device reports. Fixes: 4ea14a53d8f8 ("Input: gpio-keys - report error when disabling unsupported key") Reported-by: Ivaylo Dimitrov Tested-by: Ivaylo Dimitrov Signed-off-by: Dmitry Torokhov

Input: omap-keypad - remove dead check

2016-01-08T01:26:23Z

Commit da1f026b532ce944d74461497dc6d8c16456466e ("Keyboard: omap-keypad: use matrix_keypad.h") switched the driver to use matrix keypad infrastructure, which made array of keycodes to be unsigned short, and caused the test for negativity never trigger. This leads to the following static checker warning: drivers/input/keyboard/omap-keypad.c:158 omap_kp_tasklet() warn: 'keycodes[]' is never negative. Given that we did not care about this check for a few years already let's simply remove it. Reported-by: Dan Carpenter Acked-by: Aaro Koskinen Acked-by: Tony Lindgren Signed-off-by: Dmitry Torokhov

Input: omap-keypad - set tasklet data earlier

2016-01-07T17:57:21Z

It feels like we should set the tasklet data before enabling it. Signed-off-by: Dan Carpenter Signed-off-by: Dmitry Torokhov

Input: snvs_pwrkey - remove duplicated semicolon

2015-10-27T00:28:34Z

Remove the unneded semicolon since it is clearly a typo error. Signed-off-by: Javier Martinez Canillas Signed-off-by: Dmitry Torokhov

Input: tegra-kbc - drop use of IRQF_NO_SUSPEND flag

2015-10-26T08:39:07Z

The driver handles wakeup irq correctly using device_init_wakeup and enable_irq_wake. There's no need to use IRQF_NO_SUSPEND while registering the interrupt. This patch removes the use of IRQF_NO_SUSPEND flag. Signed-off-by: Sudeep Holla Acked-by: Thierry Reding Acked-by: Laxman Dewangan Signed-off-by: Dmitry Torokhov

Input: tegra-kbc - enable support for the standard "wakeup-source" property

2015-10-26T08:26:59Z

Though the tegra-kbc driver should/will continue to support the legacy "nvidia,wakeup-source" property to enable keyboard as the wakeup source, we need to add support for the new standard property "wakeup-source". This patch adds support for "wakeup-source" property in addition to the existing "nvidia,wakeup-source" property. Signed-off-by: Sudeep Holla Signed-off-by: Dmitry Torokhov