linux-toradex.git/drivers/input/mouse/psmouse-base.c, branch v3.2.12-rt22

Input: psmouse - switch to using dev_*() for messages

2011-10-11T01:28:16+00:00

This will ensure our reporting is consistent with the rest of the system
and we do not refer to obsolete source file names.

Reviewed-by: Wanlong Gao 
Reviewed-by: JJ Ding 
Reviewed-by: Daniel Kurtz 
Signed-off-by: Dmitry Torokhov

Input: hgpk - support GlideSensor and PenTablet modes

2010-11-12T06:21:15+00:00

Add a "hgpk_mode" sysfs attribute that allows selection between 3 options:
Mouse (the existing option), GlideSensor and PenTablet.

GlideSensor is an enhanced protocol for the regular touchpad mode that
additionally reports pressure and uses absolute coordinates. We suspect
that it may be more reliable than mouse mode in some environments.

PenTablet mode puts the touchpad into resistive mode, you must then use
a stylus as an input. We suspect this is the most reliable way to drive
the touchpad.

The GlideSensor and PenTablet devices expose themselves with the
intention of being combined with the synaptics X11 input driver.

Based on earlier work by Paul Fox.

Signed-off-by: Daniel Drake 
Signed-off-by: Dmitry Torokhov

Input: serio - support multiple child devices per single parent

2010-10-13T14:49:28+00:00

Some (rare) serio devices need to have multiple serio children. One of
the examples is PS/2 multiplexer present on several TQC STKxxx boards,
which connect PS/2 keyboard and mouse to single tty port.

Signed-off-by: Dmitry Eremin-Solenikov 
Signed-off-by: Dmitry Torokhov

param: use ops in struct kernel_param, rather than get and set fns directly

2010-08-11T13:34:13+00:00

This is more kernel-ish, saves some space, and also allows us to
expand the ops without breaking all the callers who are happy for the
new members to be NULL.

The few places which defined their own param types are changed to the
new scheme (more which crept in recently fixed in following patches).

Since we're touching them anyway, we change get() and set() to take a
const struct kernel_param (which they really are).  This causes some
harmless warnings until we fix them (in following patches).

To reduce churn, module_param_call creates the ops struct so the callers
don't have to change (and casts the functions to reduce warnings).
The modern version which takes an ops struct is called module_param_cb.

Signed-off-by: Rusty Russell 
Reviewed-by: Takashi Iwai 
Tested-by: Phil Carmody 
Cc: "David S. Miller" 
Cc: Ville Syrjala 
Cc: Dmitry Torokhov 
Cc: Alessandro Rubini 
Cc: Michal Januszewski 
Cc: Trond Myklebust 
Cc: "J. Bruce Fields" 
Cc: Neil Brown 
Cc: linux-kernel@vger.kernel.org
Cc: linux-input@vger.kernel.org
Cc: linux-fbdev-devel@lists.sourceforge.net
Cc: linux-nfs@vger.kernel.org
Cc: netdev@vger.kernel.org

Input: psmouse - small formatting changes to better follow coding style

2010-05-19T18:31:51+00:00

Signed-off-by: Dmitry Torokhov

Input: psmouse - reset all types of mice before reconnecting

2010-05-13T07:43:26+00:00

Synaptics hardware requires resetting device after suspend to ram
in order for the device to be operational. The reset lives in
synaptics-specific reconnect handler, but it is not being invoked
if synaptics support is disabled and the device is handled as a
standard PS/2 device (bare or IntelliMouse protocol).

Let's add reset into generic reconnect handler as well.

Signed-off-by: Dmitry Torokhov

Input: psmouse - ignore parity error for basic protocols

2010-04-19T07:50:42+00:00

Observing behavior of the other OS it appears that parity errors reported
by the keyboard controller are being ignored and the data is processed
as usual. Let's do the same for standard PS/2 protocols (bare, Intellimouse
and Intellimouse Explorer) to provide better compatibility. Thsi should fix
teh following bug:

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

Thanks for Damjan Jovanovic for locating the source of issue and ideas
for the patch.

Tested-by: Damjan Jovanovic 
Signed-off-by: Dmitry Torokhov

Input: psmouse - make sure we don't schedule reconnects after cleanup

2010-02-08T07:53:41+00:00

Set state of the device as "initializing" during and after cleanup
to ensure that unsolicited data from the device is not passed on.
We especially want to avoid processing new device announcements
"0xaa 0x00" that can come up before we perform reconnect operation.

Signed-off-by: Dmitry Torokhov

Input: pmouse - move Sentelic probe down the list

2010-01-13T08:28:10+00:00

Sentelic probes confuse IBM trackpoints so they stop responding to
TP_READ_ID command. See:

	http://bugzilla.kernel.org/show_bug.cgi?id=14970

Let's move FSP detection lower so it is probed after trackpoint and
others, just before we strat probing for Intellimouse Explorer.

Signed-off-by: Tai-hwa Liang 
Signed-off-by: Dmitry Torokhov

Input: psmouse - fix Synaptics detection when protocol is disabled

2010-01-07T09:53:30+00:00

For configurations where Synaptics hardware is present but the Synaptics
extensions support is not compiled in, the mouse is reprobed and a new
device is allocated on every suspend/resume.

During probe, psmouse_switch_protocol() calls psmouse_extensions() with
set_properties=1. This calls the dummy synaptics_init() which returns an
error code, instructing us not to use the synaptics extensions.

During resume, psmouse_reconnect() calls psmouse_extensions() with
set_properties=0, in which case call to synaptics_init() is bypassed and
PSMOUSE_SYNAPTICS is returned. Since the result is different from previous
attempt psmouse_reconnect() fails and full re-probe happens.

Fix this by tweaking the set_properties=0 codepath in psmouse_extensions()
to be more careful about offering PSMOUSE_SYNAPTICS extensions.

Signed-off-by: Daniel Drake 
Signed-off-by: Dmitry Torokhov