<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/input, branch v3.10.35</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/input?h=v3.10.35</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/input?h=v3.10.35'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-03-31T16:58:14Z</updated>
<entry>
<title>Input: wacom - make sure touch_max is set for touch devices</title>
<updated>2014-03-31T16:58:14Z</updated>
<author>
<name>Ping Cheng</name>
<email>pinglinux@gmail.com</email>
</author>
<published>2013-11-26T02:43:45Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c16d2409ed27ae4fabcf608e48725e1618e76064'/>
<id>urn:sha1:c16d2409ed27ae4fabcf608e48725e1618e76064</id>
<content type='text'>
commit 1d0d6df02750b4a6f466768cbfbf860e24f4c8d4 upstream.

Old single touch Tablet PCs do not have touch_max set at
wacom_features. Since touch device at lease supports one
finger, assign touch_max to 1 when touch usage is defined
in its HID Descriptor and touch_max is not pre-defined.

Tested-by: Jason Gerecke &lt;killertofu@gmail.com&gt;
Signed-off-by: Ping Cheng &lt;pingc@wacom.com&gt;
Reviewed-by: Chris Bagwell &lt;chris@cnpbagwell.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Cc: Josh Boyer &lt;jwboyer@fedoraproject.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: elantech - improve clickpad detection</title>
<updated>2014-03-31T16:58:14Z</updated>
<author>
<name>Hans de Goede</name>
<email>hdegoede@redhat.com</email>
</author>
<published>2013-12-16T15:09:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dc48b3deaebfbd6c508d258a40d417a38fa0299d'/>
<id>urn:sha1:dc48b3deaebfbd6c508d258a40d417a38fa0299d</id>
<content type='text'>
commit c15bdfd5b9831e4cab8cfc118243956e267dd30e upstream.

The current assumption in the elantech driver that hw version 3 touchpads
are never clickpads and hw version 4 touchpads are always clickpads is
wrong.

There are several bug reports for this, ie:
https://bugzilla.redhat.com/show_bug.cgi?id=1030802
http://superuser.com/questions/619582/right-elantech-touchpad-button-not-working-in-linux

I've spend a couple of hours wading through various bugzillas, launchpads
and forum posts to create a list of fw-versions and capabilities for
different laptop models to find a good method to differentiate between
clickpads and versions with separate hardware buttons.

Which shows that a device being a clickpad is reliable indicated by bit 12
being set in the fw_version. I've included the gathered list inside the
driver, so that we've this info at hand if we need to revisit this later.

Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Reviewed-by: Benjamin Tissoires &lt;benjamin.tissoires@redhat.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Cc: Josh Boyer &lt;jwboyer@fedoraproject.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input - arizona-haptics: Fix double lock of dapm_mutex</title>
<updated>2014-03-07T05:30:12Z</updated>
<author>
<name>Charles Keepax</name>
<email>ckeepax@opensource.wolfsonmicro.com</email>
</author>
<published>2014-02-18T15:22:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=790cc82a2b2b43f9d47934aab74d892c271fcbed'/>
<id>urn:sha1:790cc82a2b2b43f9d47934aab74d892c271fcbed</id>
<content type='text'>
commit c4204960e9d0ba99459dbf1db918f99a45e7a62a upstream.

snd_soc_dapm_sync takes the dapm_mutex internally, but we currently take
it externally as well. This patch fixes this.

Signed-off-by: Charles Keepax &lt;ckeepax@opensource.wolfsonmicro.com&gt;
Signed-off-by: Mark Brown &lt;broonie@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Input: allocate absinfo data when setting ABS capability</title>
<updated>2014-01-09T20:24:24Z</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=2d8ccbd72d8e44d40daa7500a5a78cc8ccad02f1'/>
<id>urn:sha1:2d8ccbd72d8e44d40daa7500a5a78cc8ccad02f1</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:45:08Z</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=c3d8edeff268c5d7c6701b238a1d75389efd899c'/>
<id>urn:sha1:c3d8edeff268c5d7c6701b238a1d75389efd899c</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: xpad - add signature for Razer Onza Classic Edition</title>
<updated>2013-12-20T15:45:06Z</updated>
<author>
<name>Mag</name>
<email>magissia@magissia.com</email>
</author>
<published>2013-08-26T07:22:01Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=17430858ee6bbf5e5f15a998ce5447f05d90b850'/>
<id>urn:sha1:17430858ee6bbf5e5f15a998ce5447f05d90b850</id>
<content type='text'>
commit ed06349fe8d12dcb718984862b6e839fc8606c34 upstream.

Signed-off-by: Nol "Mag" Archinova &lt;magissia@magissia.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:36:28Z</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=e9295a956ba01ab0cab6a7e9f6eca73da23373a8'/>
<id>urn:sha1:e9295a956ba01ab0cab6a7e9f6eca73da23373a8</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:36:28Z</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=4cdd9497f6ece54905d1df1d793b136c79123b09'/>
<id>urn:sha1:4cdd9497f6ece54905d1df1d793b136c79123b09</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: usbtouchscreen: ignore eGalax/D-Wav/EETI HIDs</title>
<updated>2013-12-04T18:57:18Z</updated>
<author>
<name>Forest Bond</name>
<email>forest.bond@rapidrollout.com</email>
</author>
<published>2013-10-21T16:38:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c2dd82b43dcc08aad0e139e23509efb195ad6fc1'/>
<id>urn:sha1:c2dd82b43dcc08aad0e139e23509efb195ad6fc1</id>
<content type='text'>
commit ae2aa3a512fa5f50f67feba9e66bc2efb394bd63 upstream.

The HID driver now handles these devices, regardless of what protocol
the device claims it supports.

Signed-off-by: Forest Bond &lt;forest.bond@rapidrollout.com&gt;
Acked-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&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:57:18Z</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=d84c1fcb5bdb1ac919fe7262505306a2ca1a6281'/>
<id>urn:sha1:d84c1fcb5bdb1ac919fe7262505306a2ca1a6281</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>
</feed>
