linux-toradex.git/drivers/input/rmi4, branch v4.13-rc2

Merge branch 'next' into for-linus

2017-07-06T20:51:43+00:00

Prepare input updates for 4.13 merge window.

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: 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: synaptics-rmi4 - use %phN to form F34 configuration ID

2017-06-02T05:11:23+00:00

Instead of printing bytes one by one, let's use %phN to print the buffer in
one go.

Also use hweight8 to count number of partitions instead of inspecting it
bit by bit.

Reviewed-by: Benjamin Tissoires 
Tested-by: Nick Dyer 
Signed-off-by: Dmitry Torokhov

Input: synaptics-rmi4 - change a char type to u8

2017-05-30T04:48:37+00:00

Smatch doesn't like when we use "%02X" to print char types because,
what about if it's a negative?

Signed-off-by: Dan Carpenter 
Signed-off-by: Dmitry Torokhov

Input: synaptics-rmi4 - enable IRQ operation in F34 V7

2017-04-14T21:52:32+00:00

The polled firmware update proved unreliable when testing on S7817. Use
attention to signal commands are complete.

Signed-off-by: Nick Dyer 
Tested-by: Chris Healy 
Acked-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov

Input: synaptics-rmi4 - change F12 clip to inactive border debug

2017-04-14T21:52:31+00:00

The data in F12_2D_Ctrl8 corresponds to the inactive border width used by
the RMI device. It is not in pixel units and should not be treated as a
clip value.

Signed-off-by: Nick Dyer 
Tested-by: Chris Healy 
Acked-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov

Input: synaptics-rmi4 - use dev_driver_string when registering interrupt

2017-04-14T21:52:29+00:00

When IRQ handling was moved to rmi_driver in 3aeed5b the naming of the
interrupt changed from "rmi4_i2c" to "2-0020" (or similar). This patch
restores the previous behaviour and makes the interrupt easier to identify
in /proc/interrupts.

Signed-off-by: Nick Dyer 
Tested-by: Chris Healy 
Acked-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov

Input: synaptics-rmi4 - when registering sensors do not call them "drivers"

2017-04-03T23:24:00+00:00

We are not registering drivers, but transport devices (AKA sensors), so
let's call them that.

Also let's rename "retval" to "error" in probe() functions as the variables
are used to store error codes.

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

Input: synaptics-rmi4 - cleanup SMbus mapping handling

2017-04-03T23:24:00+00:00

There is no reason to copy structures field-by-filed when we can copy
elements at once.

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