linux-stable.git/drivers/input/keyboard, branch linux-3.12.y

Input: mpr121 - set missing event capability

2017-04-11T06:04:40+00:00

commit 9723ddc8fe0d76ce41fe0dc16afb241ec7d0a29d upstream.

This driver reports misc scan input events on the sensor's status
register changes.  But the event capability for them was not set in the
device initialization, so these events were ignored.

This change adds the missing event capability.

Signed-off-by: Akinobu Mita 
Signed-off-by: Dmitry Torokhov 
Cc: Oliver Neukum 
Signed-off-by: Jiri Slaby

Input: mpr121 - handle multiple bits change of status register

2017-04-11T06:04:39+00:00

commit 08fea55e37f58371bffc5336a59e55d1f155955a upstream.

This driver reports input events on their interrupts which are triggered
by the sensor's status register changes.  But only single bit change is
reported in the interrupt handler.  So if there are multiple bits are
changed at almost the same time, other press or release events are ignored.

This fixes it by detecting all changed bits in the status register.

Signed-off-by: Akinobu Mita 
Signed-off-by: Dmitry Torokhov 
Cc: Oliver Neukum 
Signed-off-by: Jiri Slaby

Input: tca8418 - use the interrupt trigger from the device tree

2017-04-11T06:04:39+00:00

commit 259b77ef853cc375a5c9198cf81f9b79fc19413c upstream.

The TCA8418 might be used using different interrupt triggers on various
boards. This is not working so far because the current code forces a
falling edge trigger.

The device tree already provides a trigger type, so let's use whatever it
sets up, and since we can be loaded without DT, keep the old behaviour for
the non-DT case.

Signed-off-by: Maxime Ripard 
Signed-off-by: Dmitry Torokhov 
Cc: Oliver Neukum 
Signed-off-by: Jiri Slaby

Input: omap4-keypad - fix memory leak

2015-10-28T15:38:30+00:00

commit d79bdc7f004404204a6ac07785f8d6717070ecdb upstream.

If omap4_keypad_parse_dt() fails we returned the error code but we
missed releasing keypad_data.

Signed-off-by: Sudip Mukherjee 
Signed-off-by: Dmitry Torokhov 
Cc: Oliver Neukum 
Signed-off-by: Jiri Slaby

Input: cros_ec_keyb - fix clearing keyboard state on wakeup

2015-05-26T14:26:57+00:00

commit ef30a406468a3eae007210ae0dc5ed8d5eb59b7d upstream.

As the comment right before explains, the keyboard state is to be cleared
only if the EC wasn't a wakeup source in the last suspend.

Without this commit, there's an unneeded delay when resuming from suspend
and we also lose the key that was pressed while suspended.

Signed-off-by: Tomeu Vizoso 
Reviewed-by: Javier Martinez Canillas 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Jiri Slaby

Input: atkbd - do not try 'deactivate' keyboard on any LG laptops

2014-10-13T13:41:22+00:00

commit c01206796139e2b1feb7539bc72174fef1c6dc6e upstream.

We are getting more and more reports about LG laptops not having
functioning keyboard if we try to deactivate keyboard during probe.
Given that having keyboard deactivated is merely "nice to have"
instead of a hard requirement for probing, let's disable it on all
LG boxes instead of trying to hunt down particular models.

This change is prompted by patches trying to add "LG Electronics"/"ROCKY"
and "LG Electronics"/"LW60-F27B" to the DMI list.

https://bugzilla.kernel.org/show_bug.cgi?id=77051

Reported-by: Jaime Velasco Juan 
Reported-by: Georgios Tsalikis 
Tested-by: Jaime Velasco Juan 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Jiri Slaby

Input: atkbd - fix keyboard not working on some LG laptops

2014-06-09T13:53:28+00:00

commit 3d725caa9dcc78c3dc9e7ea0c04f626468edd9c9 upstream.

After issuing ATKBD_CMD_RESET_DIS, keyboard on some LG laptops stops
working. The workaround is to stop issuing ATKBD_CMD_RESET_DIS commands.

In order to keep changes in atkbd driver to the minimum we check DMI
signature and only skip ATKBD_CMD_RESET_DIS if we are running on LG
LW25-B7HV or P1-J273B.

Signed-off-by: Sheng-Liang Song 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Jiri Slaby

Input: allow deselecting serio drivers even without CONFIG_EXPERT

2013-12-12T06:37:55+00:00

commit bcd2623073e98f69f84720308db0b142c4da0bd6 upstream.

There is plenty of consumer hardware (e.g., mac books) that does not use AT
keyboards or PS/2 mice. It therefore makes sense for distro kernels to
build the related drivers as modules to avoid loading them on hardware that
does not need them. As such, these options should no longer be protected by
EXPERT.

Moreover, building these drivers as modules gets rid of the following ugly
error during boot:

[    2.337745] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    3.439537] i8042: No controller found

Signed-off-by: Tom Gundersen 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Greg Kroah-Hartman

Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

2013-10-31T17:38:59+00:00

Pull input updates from Dmitry Torokhov:
 "A bit later than I would want, but the changes are very minor - a few
  new device IDs for new hardware in existing drivers, fix for battery
  in Wacom devices not be considered system battery and cause emergency
  hibernations, and a couple of other bug fixes"

* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
  Input: ALPS - add support for model found on Dell XT2
  Input: wacom - add support for ISDv4 0x10E sensor
  Input: wacom - add support for ISDv4 0x10F sensor
  Input: wacom - export battery scope
  Input: cm109 - convert high volume dev_err() to dev_err_ratelimited()
  Input: move name/timer init to input_alloc_dev()
  Input: i8042 - i8042_flush fix for a full 8042 buffer
  Input: pxa27x_keypad - fix NULL pointer dereference

Input: pxa27x_keypad - fix NULL pointer dereference

2013-09-18T15:13:54+00:00

A NULL pointer dereference exception occurs in the driver probe function when
device tree is used.  The pdata pointer will be NULL in this case, but the code
dereferences it in all cases.  When device tree is used, a platform data
structure is allocated and initialized, and in all cases this pointer is copied
to the driver's private data, so the variable being tested should be accessed
through the driver's private data structure.

Signed-off-by: Mike Dunn 
Signed-off-by: Dmitry Torokhov