[PATCH 0/7] New set of input patches

From: Dmitry Torokhov
Date: Fri Nov 12 2004 - 01:37:37 EST

Hi Vojtech,

Here is the new set of input patches. Please do

bk pull bk://dtor.bkbits.net/input

It has the tonight's pull from Linus's tree plus the following patches:

Move panicbkink parameter definition together with the rest of i8042
module parameters, add description and entry in kernel-parameters.txt

Add serio start() and stop() methods to serio structure that are
called when serio port is about to be fully registered and when
serio port is about to be unregistered. These methods are useful
for drivers that share interrupt among several serio ports. In this
case interrupt can not be enabled/disabled in open/close methods
and it is very hard to determine if interrupt shoudl be ignored or
passed on.

Make use of new serio start/stop methods to safely activate and
deactivate ports. Also unify as much as possible port handling
between KBD, AUX and MUX ports. Rename i8042_values into i8042_port.

Do not submit serio event into event queue if there is already one
of the same type for the same port in front of it. Also look for
duplicat events once event is processed. This should help with
disconnected ports generating alot of data and consuming memory for
events when kseriod gets behind and prevents constant rescans.
This also allows to remove special check for 0xaa in reconnect path
of interrupt handler known to cause problems with Toshibas keyboards.

Return -EINVAL from evdev_read when passed buffer is too small.
Based on patch by James Lamanna.

Set mouse name to "Mouse" instead of leaving it NULL when using
PS2++ protocol and don't have any other information (Wheel, Touchpad)
about the mouse.

Toshiba Satellite KBCs have trouble handling data stream coming from
Synaptics at full rate (80 pps, 480 byte/sec) which causes keyboards
to pause or even get stuck. Use DMI to detect Satellites and limit
rate to 40 pps which cures keyboard.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/