<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/input, branch v2.6.32.32</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/input?h=v2.6.32.32</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/input?h=v2.6.32.32'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-02-17T23:36:59Z</updated>
<entry>
<title>input: bcm5974: Add support for MacBookAir3</title>
<updated>2011-02-17T23:36:59Z</updated>
<author>
<name>Edgar (gimli) Hucek</name>
<email>gimli@dark-green.com</email>
</author>
<published>2010-11-09T16:38:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1e81d74b8bbd77d990a367cbe380637eaa12513d'/>
<id>urn:sha1:1e81d74b8bbd77d990a367cbe380637eaa12513d</id>
<content type='text'>
commit 6021afcf19d8c6f5db6d11cadcfb6a22d0c28a48 upstream.

This patch adds support for the MacBookAir3,1 and MacBookAir3,2
models.

[rydberg@euromail.se: touchpad range calibration]
Signed-off-by: Edgar (gimli) Hucek &lt;gimli@dark-green.com&gt;
Signed-off-by: Henrik Rydberg &lt;rydberg@euromail.se&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: i8042 - introduce 'notimeout' blacklist for Dell Vostro V13</title>
<updated>2011-02-17T23:36:58Z</updated>
<author>
<name>Jiri Kosina</name>
<email>jkosina@suse.cz</email>
</author>
<published>2011-01-08T09:37:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=366bc80896e5789386d6cf81189dad4106e64712'/>
<id>urn:sha1:366bc80896e5789386d6cf81189dad4106e64712</id>
<content type='text'>
commit f8313ef1f448006207f12c107123522c8bc00f15 upstream.

i8042 controller present in Dell Vostro V13 errorneously signals spurious
timeouts.

Introduce i8042.notimeout parameter for ignoring i8042-signalled timeouts
and apply this quirk automatically for Dell Vostro V13, based on DMI match.

In addition to that, this machine also needs to be added to nomux blacklist.

Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Cc: Tim Gardner &lt;tcanonical@tpi.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: i8042 - add Sony VAIO VPCZ122GX to nomux list</title>
<updated>2010-12-09T21:27:08Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2010-11-04T16:12:44Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a22280783f150f3e0bd03b4124faa73d45b8af06'/>
<id>urn:sha1:a22280783f150f3e0bd03b4124faa73d45b8af06</id>
<content type='text'>
[Note that the mainline will not have this particular fix but rather
will blacklist entire VAIO line based off DMI board name. For stable
I am being a bit more cautious and blacklist one particular product.]

Trying to query/activate active multiplexing mode on this VAIO makes
both keyboard and touchpad inoperable. Futher kernels will blacklist
entire VAIO line, however here we blacklist just one particular model.

Reported-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: joydev - fix JSIOCSAXMAP ioctl</title>
<updated>2010-10-29T04:43:59Z</updated>
<author>
<name>Kenneth Waters</name>
<email>kwwaters@gmail.com</email>
</author>
<published>2010-09-21T07:58:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0bed849274ba1408e45805000a13ccb1c94de4df'/>
<id>urn:sha1:0bed849274ba1408e45805000a13ccb1c94de4df</id>
<content type='text'>
commit d2520a426dc3033c00077e923a553fc6c98c7564 upstream.

Fixed JSIOCSAXMAP ioctl to update absmap, the map from hardware axis to
event axis in addition to abspam.  This fixes a regression introduced
by 999b874f.

Signed-off-by: Kenneth Waters &lt;kwwaters@gmail.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: add compat support for sysfs and /proc capabilities output</title>
<updated>2010-09-27T00:21:38Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2010-01-11T08:05:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e1155f2ae2c0562b4efe8b2b5165ad911be0d008'/>
<id>urn:sha1:e1155f2ae2c0562b4efe8b2b5165ad911be0d008</id>
<content type='text'>
commit 15e184afa83a45cf8bafdb9dc906b97a8fbc974f upstream.

Input core displays capabilities bitmasks in form of one or more longs printed
in hex form and separated by spaces. Unfortunately it does not work well
for 32-bit applications running on 64-bit kernels since applications expect
that number is "worth" only 32 bits when kernel advances by 64 bits.

Fix that by ensuring that output produced for compat tasks uses 32-bit units.

Reported-and-tested-by: Michael Tokarev &lt;mjt@tls.msk.ru&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: i8042 - fix device removal on unload</title>
<updated>2010-09-20T20:17:54Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2010-09-01T00:27:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e3327857e9b33f2cb9921e469f9ea1806fdedc9b'/>
<id>urn:sha1:e3327857e9b33f2cb9921e469f9ea1806fdedc9b</id>
<content type='text'>
commit af045b86662f17bf130239a65995c61a34f00a6b upstream.

We need to call platform_device_unregister(i8042_platform_device)
before calling platform_driver_unregister() because i8042_remove()
resets i8042_platform_device to NULL. This leaves the platform device
instance behind and prevents driver reload.

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

Reported-by: Seryodkin Victor &lt;vvscore@gmail.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: twl40300-keypad - fix handling of "all ground" rows</title>
<updated>2010-08-02T17:20:55Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2010-07-21T03:25:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7f9079606b66c6c477406108fba53bdd4f58b10b'/>
<id>urn:sha1:7f9079606b66c6c477406108fba53bdd4f58b10b</id>
<content type='text'>
commit 3fea60261e73dbf4a51130d40cafcc8465b0f2c3 upstream.

The Nokia RX51 board code (arch/arm/mach-omap2/board-rx51-peripherals.c)
defines a key map for the matrix keypad keyboard. The hardware seems to
use all of the 8 rows and 8 columns of the keypad, although not all
possible locations are used.

The TWL4030 supports keypads with at most 8 rows and 8 columns. Most keys
are defined with a row and column number between 0 and 7, except

        KEY(0xff, 2, KEY_F9),
        KEY(0xff, 4, KEY_F10),
        KEY(0xff, 5, KEY_F11),

which represent keycodes that should be emitted when entire row is
connected to the ground.  since the driver handles this case as if we
had an extra column in the key matrix. Unfortunately we do not allocate
enough space and end up owerwriting some random memory.

Reported-and-tested-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: i8042 - add Gigabyte Spring Peak to dmi_noloop_table</title>
<updated>2010-08-02T17:20:54Z</updated>
<author>
<name>Kamal Mostafa</name>
<email>kamal@canonical.com</email>
</author>
<published>2010-07-19T18:00:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b80374e2606aa788acb6debf95c1f97b0308f851'/>
<id>urn:sha1:b80374e2606aa788acb6debf95c1f97b0308f851</id>
<content type='text'>
commit 3e1bbc8d5018a05c0793c8a32b777a1396eb4414 upstream.

Gigabyte "Spring Peak" notebook indicates wrong chassis-type, tripping up
i8042 and breaking the touchpad.  Add this model to i8042_dmi_noloop_table[]
to resolve.

BugLink: https://bugs.launchpad.net/bugs/580664

Signed-off-by: Kamal Mostafa &lt;kamal@canonical.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: psmouse - reset all types of mice before reconnecting</title>
<updated>2010-07-05T18:11:16Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2010-05-13T07:42:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=04a08885c36dc2f4663900d007b9d71a7e7f2b92'/>
<id>urn:sha1:04a08885c36dc2f4663900d007b9d71a7e7f2b92</id>
<content type='text'>
commit ef110b24e28f36620f63dab94708a17c7e267358 upstream.

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 &lt;dtor@mail.ru&gt;
Cc: Tim Gardner &lt;tim.gardner@canonical.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Input: wacom - switch mode upon system resume</title>
<updated>2010-04-26T14:41:34Z</updated>
<author>
<name>Ping Cheng</name>
<email>pingc@wacom.com</email>
</author>
<published>2010-04-19T18:10:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4186c4e6ebec12c705065b353c5fd7a1a87eea7d'/>
<id>urn:sha1:4186c4e6ebec12c705065b353c5fd7a1a87eea7d</id>
<content type='text'>
commit 014f61504af276ba9d9544d8a7401d8f8526eb73 upstream.

When Wacom devices wake up from a sleep, the switch mode command
(wacom_query_tablet_data) is needed before wacom_open is called.
wacom_query_tablet_data should not be executed inside wacom_open
since wacom_open is called more than once during probe.

Reported-and-tested-by: Anton Anikin &lt;Anton@Anikin.name&gt;
Signed-off-by: Ping Cheng &lt;pingc@wacom.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
