<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/input, branch v3.4.80</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/input?h=v3.4.80</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/input?h=v3.4.80'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-01-08T17:42:12Z</updated>
<entry>
<title>Input: allocate absinfo data when setting ABS capability</title>
<updated>2014-01-08T17:42:12Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2013-12-27T01:44:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1b01494b82bf4f46821dd4dda2bb35aa43415eeb'/>
<id>urn:sha1:1b01494b82bf4f46821dd4dda2bb35aa43415eeb</id>
<content type='text'>
commit 28a2a2e1aedbe2d8b2301e6e0e4e63f6e4177aca upstream.

We need to make sure we allocate absinfo data when we are setting one of
EV_ABS/ABS_XXX capabilities, otherwise we may bomb when we try to emit this
event.

Rested-by: Paul Cercueil &lt;pcercuei@gmail.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: usbtouchscreen - separate report and transmit buffer size handling</title>
<updated>2013-12-20T15:34:20Z</updated>
<author>
<name>Christian Engelmayer</name>
<email>christian.engelmayer@frequentis.com</email>
</author>
<published>2013-11-27T02:16:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=13970f80f2b64e819732f605e0a18f558ccb7166'/>
<id>urn:sha1:13970f80f2b64e819732f605e0a18f558ccb7166</id>
<content type='text'>
commit 4ef38351d770cc421f4a0c7a849fd13207fc5741 upstream.

This patch supports the separate handling of the USB transfer buffer length
and the length of the buffer used for multi packet support. For devices
supporting multiple report or diagnostic packets, the USB transfer size is now
limited to the USB endpoints wMaxPacketSize - otherwise it defaults to the
configured report packet size as before.

This fixes an issue where event reporting can be delayed for an arbitrary
time for multi packet devices. For instance the report size for eGalax devices
is defined to the 16 byte maximum diagnostic packet size as opposed to the 5
byte report packet size. In case the driver requests 16 byte from the USB
interrupt endpoint, the USB host controller driver needs to split up the
request into 2 accesses according to the endpoints wMaxPacketSize of 8 byte.
When the first transfer is answered by the eGalax device with not less than
the full 8 byte requested, the host controller has got no way of knowing
whether the touch controller has got additional data queued and will issue
the second transfer. If per example a liftoff event finishes at such a
wMaxPacketSize boundary, the data will not be available to the usbtouch driver
until a further event is triggered and transfered to the host. From user
perspective the BTN_TOUCH release event in this case is stuck until the next
touch down event.

Signed-off-by: Christian Engelmayer &lt;christian.engelmayer@frequentis.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: mousedev - allow disabling even without CONFIG_EXPERT</title>
<updated>2013-12-12T06:34:11Z</updated>
<author>
<name>Tom Gundersen</name>
<email>teg@jklm.no</email>
</author>
<published>2013-10-31T07:44:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5beebfa585c2348312b5934e588acbb97246765b'/>
<id>urn:sha1:5beebfa585c2348312b5934e588acbb97246765b</id>
<content type='text'>
commit dfaaed08ecc01bd513248ba7999daf50ce028352 upstream.

Moust (if not all) modern software, including X, uses /dev/eventX rather than
the legacy /dev/mouseX devices. It therefore makes sense for general-purpose
(distro) kernels to use MOUSEDV=m (or even n), so let's drop the EXPERT=y
requirement.

Signed-off-by: Tom Gundersen &lt;teg@jklm.no&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: allow deselecting serio drivers even without CONFIG_EXPERT</title>
<updated>2013-12-12T06:34:11Z</updated>
<author>
<name>Tom Gundersen</name>
<email>teg@jklm.no</email>
</author>
<published>2013-10-31T07:38:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=315a93764c1fa8bdbe9ab867d896a0d9478b54ed'/>
<id>urn:sha1:315a93764c1fa8bdbe9ab867d896a0d9478b54ed</id>
<content type='text'>
commit bcd2623073e98f69f84720308db0b142c4da0bd6 upstream.

There is plenty of consumer hardware (e.g., mac books) that does not use AT
keyboards or PS/2 mice. It therefore makes sense for distro kernels to
build the related drivers as modules to avoid loading them on hardware that
does not need them. As such, these options should no longer be protected by
EXPERT.

Moreover, building these drivers as modules gets rid of the following ugly
error during boot:

[    2.337745] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    3.439537] i8042: No controller found

Signed-off-by: Tom Gundersen &lt;teg@jklm.no&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: i8042 - add PNP modaliases</title>
<updated>2013-12-04T18:50:34Z</updated>
<author>
<name>Tom Gundersen</name>
<email>teg@jklm.no</email>
</author>
<published>2013-10-31T07:33:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1fefeae75801ca98b2693ef6b2974f0539f43e29'/>
<id>urn:sha1:1fefeae75801ca98b2693ef6b2974f0539f43e29</id>
<content type='text'>
commit 78551277e4df57864b0b0e7f85c23ede2be2edb8 upstream.

This allows the module to be autoloaded in the common case.

In order to work on non-PnP systems the module should be compiled in or
loaded unconditionally at boot (c.f. modules-load.d(5)), as before.

Signed-off-by: Tom Gundersen &lt;teg@jklm.no&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: cyttsp - fix memcpy size param</title>
<updated>2013-06-27T18:27:33Z</updated>
<author>
<name>Ferruh Yigit</name>
<email>fery@cypress.com</email>
</author>
<published>2013-05-23T16:56:55Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8c428c194065e000d4138123f147bc74f7532bbc'/>
<id>urn:sha1:8c428c194065e000d4138123f147bc74f7532bbc</id>
<content type='text'>
commit d2983cdb480157f637df07723f28aaa657b1080d upstream.

memcpy param is wrong because of offset in bl_cmd, this may corrupt the
stack which may cause a crash.

Tested-by: Ferruh Yigit &lt;fery@cypress.com&gt; on TMA300-DVK
Signed-off-by: Ferruh Yigit &lt;fery@cypress.com&gt;
Acked-by: Javier Martinez Canillas &lt;javier@dowhile0.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: sentelic - only report position of first finger as ST coordinates</title>
<updated>2013-01-11T17:06:56Z</updated>
<author>
<name>Christophe TORDEUX</name>
<email>christophe@tordeux.net</email>
</author>
<published>2012-12-24T17:20:40Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1a37441ae4ad38d98c39b349137c0fb7f76b32ad'/>
<id>urn:sha1:1a37441ae4ad38d98c39b349137c0fb7f76b32ad</id>
<content type='text'>
commit a25461659050b913e114d282bf58823682eb56b6 upstream.

Report only the position of the first finger as absolute non-MT coordinates,
instead of reporting both fingers alternatively. Actual MT events are
unaffected.

This fixes horizontal and improves vertical scrolling with the touchpad.

Signed-off-by: Christophe TORDEUX &lt;christophe@tordeux.net&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: walkera0701 - fix crash on startup</title>
<updated>2013-01-11T17:06:56Z</updated>
<author>
<name>Peter Popovec</name>
<email>popovec@oko.fei.tuke.sk</email>
</author>
<published>2012-12-15T06:57:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c815c83dfd1aef11d4197dc46b21a2471b81af2c'/>
<id>urn:sha1:c815c83dfd1aef11d4197dc46b21a2471b81af2c</id>
<content type='text'>
commit a455e2985f57e2a71566bb8850094af38b2c932d upstream.

The driver's timer must be set up before enabling IRQ handler, otherwise
bad things may happen.

Reported-and-tested-by: Fengguang Wu &lt;fengguang.wu@intel.com&gt;
Signed-off-by: Peter Popovec &lt;popovec@fei.tuke.sk&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>x86, 8042: Enable A20 using KBC to fix S3 resume on some MSI laptops</title>
<updated>2013-01-11T17:06:44Z</updated>
<author>
<name>Ondrej Zary</name>
<email>linux@rainbow-software.org</email>
</author>
<published>2012-12-11T21:18:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4511ba021ea5ee7f2b76d954fc23c3814ac07cba'/>
<id>urn:sha1:4511ba021ea5ee7f2b76d954fc23c3814ac07cba</id>
<content type='text'>
commit ad68652412276f68ad4fe3e1ecf5ee6880876783 upstream.

Some MSI laptop BIOSes are broken - INT 15h code uses port 92h to enable A20
line but resume code assumes that KBC was used.
The laptop will not resume from S3 otherwise but powers off after a while
and then powers on again stuck with a blank screen.

Fix it by enabling A20 using KBC in i8042_platform_init for x86.

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

Signed-off-by: Ondrej Zary &lt;linux@rainbow-software.org&gt;
Cc: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Cc: Alan Cox &lt;alan@lxorguk.ukuu.org.uk&gt;
Cc: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Link: http://lkml.kernel.org/r/201212112218.06551.linux@rainbow-software.org
Signed-off-by: H. Peter Anvin &lt;hpa@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: tsc40 - remove wrong announcement of pressure support</title>
<updated>2012-11-17T21:15:55Z</updated>
<author>
<name>Rolf Eike Beer</name>
<email>eike-kernel@sf-tec.de</email>
</author>
<published>2012-10-31T06:39:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=180bed351c02841004ee1c9d45a7efb1e207acf1'/>
<id>urn:sha1:180bed351c02841004ee1c9d45a7efb1e207acf1</id>
<content type='text'>
commit 32ed1911fc79908d704023317d4ddeb3883fd07e upstream.

The tsc40 driver announces it supports the pressure event, but will never
send one. The announcement will cause tslib to wait for such events and
sending all touch events with a pressure of 0. Removing the announcement
will make tslib fall back to emulating the pressure on touch events so
everything works as expected.

Signed-off-by: Rolf Eike Beer &lt;eike-kernel@sf-tec.de&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

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