linux.git/drivers/input/mouse, branch v4.10-rc2

Replace with globally

2016-12-24T19:46:01+00:00

This was entirely automated, using the script by Al:

  PATT='^[[:blank:]]*#[[:blank:]]*include[[:blank:]]*'
  sed -i -e "s!$PATT!#include !" \
        $(git grep -l "$PATT"|grep -v ^include/linux/uaccess.h)

to do the replacement at the end of the merge window.

Requested-by: Al Viro 
Signed-off-by: Linus Torvalds

Merge branch 'next' into for-linus

2016-12-16T17:31:17+00:00

Prepare input updates for 4.10 merge window.

Input: ALPS - fix protcol -> protocol

2016-12-12T19:26:22+00:00

Signed-off-by: Marcos Paulo de Souza 
Reviewed-by: Pali Rohár 
Signed-off-by: Dmitry Torokhov

Input: ALPS - clean up code for SS5 hardware

2016-11-29T04:24:07+00:00

The return value of alps_get_pkt_id_ss4_v2() should really be "enum
SS4_PACKET_ID", not "unsigned char".  Correct this.

Also, most of the Alps SS5 (SS4 v2) packet byte parsing code is implemented
using macros, but there are a few places where bytes are directly
manipulated in alps.c.  For consistency, migrate the rest of these to
macros.

Reviewed-by: Pali Rohár 
Signed-off-by: Paul Donohue 
Signed-off-by: Dmitry Torokhov

Input: ALPS - clean up TrackStick handling for SS5 hardware

2016-11-29T04:24:06+00:00

For consistency and clarity, the input_report_*() functions should be
called by alps_process_packet_ss4_v2() instead of by alps_decode_ss4_v2().

Reviewed-by: Pali Rohár 
Signed-off-by: Paul Donohue 
Signed-off-by: Dmitry Torokhov

Input: ALPS - fix TrackStick support for SS5 hardware

2016-11-29T04:24:05+00:00

The current Alps SS5 (SS4 v2) code generates bogus TouchPad events when
TrackStick packets are processed.

This causes the xorg synaptics driver to print
"unable to find touch point 0" and
"BUG: triggered 'if (priv->num_active_touches > priv->num_slots)'"
messages.  It also causes unexpected TouchPad button release and re-click
event sequences if the TrackStick is moved while holding a TouchPad
button.

This commit corrects the problem by adjusting alps_process_packet_ss4_v2()
so that it only sends TrackStick reports when processing TrackStick
packets.

Reviewed-by: Pali Rohár 
Signed-off-by: Paul Donohue 
Signed-off-by: Dmitry Torokhov

Input: psmouse - disable automatic probing of BYD touchpads

2016-11-17T01:25:31+00:00

BYD automatic protocol detection is extremely unreliable and is often
triggers false positives on regular mice, Sentelic touchpads, and other
devices. BYD has several documents that have recommended detection
sequence, but they conflict with each other and, as far as I can see, still
would not produce unique enough output to reliably differentiate BYD from
other PS/2 devices.

OEMs sourcing BYD devices also do not do us any favors by not supplying any
reasonable DMI data and instead leaving turds like "To Be Filled By O.E.M."
in place of vendor data, or "System Serial Number" as serial number.

On top of that BYD is not truly modern multitouch controller, but rather a
single-touch transitional device that only reports absolute coordinates at
the beginning of finger contact and then reverts to reporting
displacements, and thus not very precise; the only benefit from using BYD
mode vs the legacy PS/2 mode is possibility of edge scrolling.

Given the above, and the fact that BYD devices are somewhat uncommon, let's
disable automatic detection of BYD devices. Users who know they have BYD
trackpads or want to experiment can attempt to activate BYD protocol via
sysfs:

	echo -n "byd" > /sys/bus/serio/devices/serio1/drvctl

Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=151691
Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=175421
Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=120781
Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=121281
Fixes: 98ee37714493 ("Input: byd - add BYD PS/2 touchpad driver")
Cc: stable@vger.kernel.org # 4.6+
Reviewed-by: Pali Rohár 
Signed-off-by: Dmitry Torokhov

Input: elan_i2c - always output the device information

2016-10-26T23:48:15+00:00

it's always easier to retrieve these information in bug reports when
it is always printed in the dmesg.

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

Input: psmouse - cleanup Focaltech code

2016-10-25T00:19:25+00:00

psmouse->name "Focaltech Touchpad" is an overkill. In xinput it is too long
as "FocaltechPS/2 Focaltech Focaltech Touchpad"

In focaltech_report_state() pointer to psmouse->dev is already stored as
*dev

Signed-off-by: Dmitry Tunin 
Signed-off-by: Dmitry Torokhov

Input: elantech - add Fujitsu Lifebook E556 to force crc_enabled

2016-10-07T23:30:12+00:00

Another Lifebook machine that needs the same quirk as other similar
models to make the driver working.

Also let's reorder elantech_dmi_force_crc_enabled list so LIfebook enries
are in alphabetical order.

Reported-by: William Linna 
Tested-by: William Linna 
Reviewed-by: Benjamin Tissoires 
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov