linux.git/drivers/input, branch v4.12

Input: synaptics-rmi4 - only read the F54 query registers which are used

2017-06-23T07:08:48+00:00

The F54 driver is currently only using the first 6 bytes of F54 so there is
no need to read all 27 bytes. Some Dell systems (Dell XP13 9333 and
similar) have an issue with the touchpad or I2C bus when reading reports
larger then 16 bytes. Reads larger then 16 bytes are reported in two HID
reports. Something about the back to back reports seems to cause the next
read to report incorrect data. This results in F30 failing to load and the
click button failing to work.

Previous issues with the I2C controller or touchpad were addressed in:
commit 5b65c2a02966 ("HID: rmi: check sanity of the incoming report")

Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=195949
Signed-off-by: Andrew Duggan 
Reviewed-by: Benjamin Tissoires 
Reviewed-by: Nick Dyer 
Signed-off-by: Dmitry Torokhov

Input: i8042 - add Fujitsu Lifebook AH544 to notimeout list

2017-06-20T03:10:15+00:00

Without this quirk, the touchpad is not responsive on this product, with
the following message repeated in the logs:

 psmouse serio1: bad data from KBC - timeout

Add it to the notimeout list alongside other similar Fujitsu laptops.

Signed-off-by: Daniel Drake 
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov

Input: soc_button_array - fix leaking the ACPI button descriptor buffer

2017-06-18T22:12:03+00:00

We are passing a buffer with ACPI_ALLOCATE_BUFFER set to
acpi_evaluate_object, so we must free it when we are done with it.

Signed-off-by: Hans de Goede 
Signed-off-by: Dmitry Torokhov

Input: synaptics-rmi4 - register F03 port as pass-through serio

2017-06-09T16:57:19+00:00

The 5th generation Thinkpad X1 Carbons use Synaptics touchpads accessible
over SMBus/RMI, combined with ALPS or Elantech trackpoint devices instead
of classic IBM/Lenovo trackpoints. Unfortunately there is no way for ALPS
driver to detect whether it is dealing with touchpad + trackpoint
combination or just a trackpoint, so we end up with a "phantom" dualpoint
ALPS device in addition to real touchpad and trackpoint.

Given that we do not have any special advanced handling for ALPS or
Elantech trackpoints (unlike IBM trackpoints that have separate driver and
a host of options) we are better off keeping the trackpoints in PS/2
emulation mode. We achieve that by setting serio type to SERIO_PS_PSTHRU,
which will limit number of protocols psmouse driver will try. In addition
to getting rid of the "phantom" touchpads, this will also speed up probing
of F03 pass-through port.

Reported-by: Damjan Georgievski 
Suggested-by: Benjamin Tissoires 
Acked-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov

Input: elantech - add Fujitsu Lifebook E546/E557 to force crc_enabled

2017-06-07T17:32:10+00:00

The Lifebook E546 and E557 touchpad were also not functioning and
worked after running:

        echo "1" > /sys/devices/platform/i8042/serio2/crc_enabled

Add them to the list of machines that need this workaround.

Signed-off-by: Ulrik De Bie 
Reviewed-by: Arjan Opmeer 
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov

Input: axp20x-pek - switch to acpi_dev_present and check for ACPI0011 too

2017-06-03T00:53:20+00:00

acpi_dev_found checks that there is a matching ACPI node, but it
may be disabled (_STA method returns 0) in which case the
soc_button_array driver will not bind to it and axp20x-pek should
handle the power-button.

This commit switches from acpi_dev_found to acpi_dev_present to
avoid not registering an input-dev for the powerbutton when there
is a disabled PNP0C40 device.

The ACPI-6.0 standard defines a standard gpio button device using
the ACPI0011 HID replacing the custom PNP0C40 gpio device, many
newer devices define both PNP0C40 and ACPI0011 devices enabling one
or the other depending on whether the BIOS thinks it is going to boot
Android or Windows.

This commit adds a check for the ACPI0011 device, so that if
either device is present *and* enabled we don't register an input-dev
for the powerbutton.

Signed-off-by: Hans de Goede 
Signed-off-by: Dmitry Torokhov

Input: axp20x-pek - only check for "INTCFD9" ACPI device on Cherry Trail

2017-06-03T00:53:19+00:00

Commit 9b13a4ca8d2c ("Input: axp20x-pek - do not register input device
on some systems") added a check for the INTCFD9 ACPI device which also
handles the powerbutton as on some systems the powerbutton is connected
to both the PMIC, handled by axp20x-pek, and to a gpio on the SoC, handled
by soc_button_array which attaches itself to the INTCFD9 ACPI device.

Testing + comparing DSDTs has shown that this only happens on Cherry
Trail devices with an AXP288 PMIC, the AXP288 PMIC is also used on
Bay Trail devices but there the power button is only connected to
the PMIC and not handled by soc_button_array.

This means that the INTCFD9 check has caused a regression on Bay Trail
devices, causing power-button presses to no longer be seen.

This commit fixes this by limiting the check to devices where the ACPI
node for the AXP288 contains a _HRV (hardware revision) attribute with
a value of 3 which indicates we are dealing with a Cherry Trail platform.

Fixes: 9b13a4ca8d2c ("Input: axp20x-pek - do not register input ...")
Reported-by: Сергей Трусов 
Signed-off-by: Hans de Goede 
Signed-off-by: Dmitry Torokhov

Merge tag 'v4.12-rc3' into for-linus

2017-06-03T00:49:10+00:00

Merge with mainline to get acpi_dev_present() needed by patches to
axp20x-pek driver.

Input: tm2-touchkey - use LEN_ON as boolean value instead of LED_FULL

2017-06-02T05:08:05+00:00

Commit 4e552c8cb5bc ("leds: add LED_ON brightness as boolean value")
has introduced the LED_ON enumeration value that can be used
instead of LED_FULL which has more of a linear value.

Because the tm2-touchscreen doesn't have brightness levels, but
it's a simple on/off led, use LED_ON instead of LED_FULL.

Signed-off-by: Andi Shyti 
Reviewed-by: Jaechul Lee 
Tested-by: Jaechul Lee 
Signed-off-by: Dmitry Torokhov

Input: synaptics - tell users to report when they should be using rmi-smbus

2017-05-30T03:00:26+00:00

Users should really consider switching to rmi-smbus instead of plain PS/2.
Notify them that they should report a missing pnpID in the file.

Signed-off-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov