<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/input, branch v2.6.38.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/input?h=v2.6.38.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/input?h=v2.6.38.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-03-23T20:04:10Z</updated>
<entry>
<title>Input: bcm5974 - add support for MacBookPro8</title>
<updated>2011-03-23T20:04:10Z</updated>
<author>
<name>Andy Botting</name>
<email>andy@andybotting.com</email>
</author>
<published>2011-03-13T04:27:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0616af64f42d534de2440d35cb25cd21a820a473'/>
<id>urn:sha1:0616af64f42d534de2440d35cb25cd21a820a473</id>
<content type='text'>
commit 47340bd9fefb571888836da942b5aee0e85e959c upstream.

This patch add multitouch support for the MacBookPro8,1 and
MacBookPro8,2 models.

Signed-off-by: Andy Botting &lt;andy@andybotting.com&gt;
Signed-off-by: Henrik Rydberg &lt;rydberg@euromail.se&gt;
Acked-by: Jiri Kosina &lt;jkosina@suse.cz&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>Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input</title>
<updated>2011-02-23T22:44:25Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2011-02-23T22:44:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=57949e8006de9643ac95447143e0211be3ff5f81'/>
<id>urn:sha1:57949e8006de9643ac95447143e0211be3ff5f81</id>
<content type='text'>
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
  Input: serio/gameport - use 'long' system workqueue
  Input: synaptics - document 0x0c query
  Input: tegra-kbc - add function keymap
</content>
</entry>
<entry>
<title>Input: serio/gameport - use 'long' system workqueue</title>
<updated>2011-02-23T16:53:07Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2011-02-23T16:51:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1d64b655dc083df5c5ac39945ccbbc6532903bf1'/>
<id>urn:sha1:1d64b655dc083df5c5ac39945ccbbc6532903bf1</id>
<content type='text'>
Commit 8ee294cd9def0004887da7f44b80563493b0a097 converted serio
subsystem event handling from using a dedicated thread to using
common workqueue. Unfortunately, this regressed our boot times,
due to the fact that serio jobs take long time to execute. While
the new concurrency managed workqueue code manages long-playing
works just fine and schedules additional workers as needed, such
works wreck havoc among remaining users of flush_scheduled_work().

To solve this problem let's move serio/gameport works from system_wq
to system_long_wq which nobody tries to flush.

Reported-and-tested-by: Hernando Torque &lt;pantherchen@versanet.de&gt;
Acked-by: Tejun Heo &lt;tj@kernel.org&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
</content>
</entry>
<entry>
<title>Input: synaptics - document 0x0c query</title>
<updated>2011-02-23T16:53:01Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2011-02-23T04:15:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9bb794ae0509f39abad6593793ec86d490bad31b'/>
<id>urn:sha1:9bb794ae0509f39abad6593793ec86d490bad31b</id>
<content type='text'>
Since Synaptics technical writers department is a bit slow releasing updated
Synaptics interface guide, let's add some new bits (with their blessing)
to the code so that they don't get lost.

Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
</content>
</entry>
<entry>
<title>Input: tegra-kbc - add function keymap</title>
<updated>2011-02-18T16:39:03Z</updated>
<author>
<name>Rakesh Iyer</name>
<email>riyer@nvidia.com</email>
</author>
<published>2011-02-18T16:38:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4e8b65f606b9e4e6922fd17a772fe3e69cc5553b'/>
<id>urn:sha1:4e8b65f606b9e4e6922fd17a772fe3e69cc5553b</id>
<content type='text'>
Add Fn keymap support to allow for internal processing of Fn keys.

Signed-off-by: Rakesh Iyer &lt;riyer@nvidia.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
</content>
</entry>
<entry>
<title>Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input</title>
<updated>2011-02-15T17:40:27Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2011-02-15T17:40:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=87450bd55d6f7caa472b5db49a97ca373baf2577'/>
<id>urn:sha1:87450bd55d6f7caa472b5db49a97ca373baf2577</id>
<content type='text'>
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
  Input: matrix_keypad - increase the limit of rows and columns
  Input: wacom - fix error path in wacom_probe()
  Input: ads7846 - check proper condition when freeing gpio
  Revert "Input: do not pass injected events back to the originating handler"
  Input: sysrq - rework re-inject logic
  Input: serio - clear pending rescans after sysfs driver rebind
  Input: rotary_encoder - use proper irqflags
  Input: wacom_w8001 - report resolution to userland
</content>
</entry>
<entry>
<title>Input: wacom - fix error path in wacom_probe()</title>
<updated>2011-02-11T09:01:15Z</updated>
<author>
<name>Alexander Strakh</name>
<email>cromlehg@gmail.com</email>
</author>
<published>2011-02-11T08:44:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4b6d44344000ff3e62faf595e5f89fd8d9e52a94'/>
<id>urn:sha1:4b6d44344000ff3e62faf595e5f89fd8d9e52a94</id>
<content type='text'>
If we fail to retrieve HID descriptor we need to free allocated URB so
jump to proper label to do that.

Signed-off-by: Alexander Strakh &lt;strakh@ispras.ru&gt;
Acked-by: Henrik Rydberg &lt;rydberg@euromail.se&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
</content>
</entry>
<entry>
<title>Input: ads7846 - check proper condition when freeing gpio</title>
<updated>2011-02-11T08:58:24Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2011-02-04T08:37:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0fbc9fdb7e747500111dcc4a5f5f3ceed0360d71'/>
<id>urn:sha1:0fbc9fdb7e747500111dcc4a5f5f3ceed0360d71</id>
<content type='text'>
When driver uses custom pendown detection method gpio_pendown is not
set up and so we should not try to free it, otherwise we are presented
with:

------------[ cut here ]------------
WARNING: at drivers/gpio/gpiolib.c:1258 gpio_free+0x100/0x12c()
Modules linked in:
[&lt;c0061208&gt;] (unwind_backtrace+0x0/0xe4) from [&lt;c0091f58&gt;](warn_slowpath_common+0x4c/0x64)
[&lt;c0091f58&gt;] (warn_slowpath_common+0x4c/0x64) from [&lt;c0091f88&gt;](warn_slowpath_null+0x18/0x1c)
[&lt;c0091f88&gt;] (warn_slowpath_null+0x18/0x1c) from [&lt;c024e610&gt;](gpio_free+0x100/0x12c)
[&lt;c024e610&gt;] (gpio_free+0x100/0x12c) from [&lt;c03e9fbc&gt;](ads7846_probe+0xa38/0xc5c)
[&lt;c03e9fbc&gt;] (ads7846_probe+0xa38/0xc5c) from [&lt;c02cff14&gt;](spi_drv_probe+0x18/0x1c)
[&lt;c02cff14&gt;] (spi_drv_probe+0x18/0x1c) from [&lt;c028bca4&gt;](driver_probe_device+0xc8/0x184)
[&lt;c028bca4&gt;] (driver_probe_device+0xc8/0x184) from [&lt;c028bdc8&gt;](__driver_attach+0x68/0x8c)
[&lt;c028bdc8&gt;] (__driver_attach+0x68/0x8c) from [&lt;c028b4c8&gt;](bus_for_each_dev+0x48/0x74)
[&lt;c028b4c8&gt;] (bus_for_each_dev+0x48/0x74) from [&lt;c028ae08&gt;](bus_add_driver+0xa0/0x220)
[&lt;c028ae08&gt;] (bus_add_driver+0xa0/0x220) from [&lt;c028c0c0&gt;](driver_register+0xa8/0x134)
[&lt;c028c0c0&gt;] (driver_register+0xa8/0x134) from [&lt;c0050550&gt;](do_one_initcall+0xcc/0x1a4)
[&lt;c0050550&gt;] (do_one_initcall+0xcc/0x1a4) from [&lt;c00084e4&gt;](kernel_init+0x14c/0x214)
[&lt;c00084e4&gt;] (kernel_init+0x14c/0x214) from [&lt;c005b494&gt;](kernel_thread_exit+0x0/0x8)
---[ end trace 4053287f8a5ec18f ]---

Also rearrange ads7846_setup_pendown() to have only one exit point
returning success.

Reported-by: Sourav Poddar &lt;sourav.poddar@ti.com&gt;
Acked-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Reviewed-by: Charulatha V &lt;charu@ti.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
</content>
</entry>
<entry>
<title>arm/ixp4xx: Rename FREQ macro to avoid collisions</title>
<updated>2011-02-06T15:49:48Z</updated>
<author>
<name>Ben Hutchings</name>
<email>ben@decadent.org.uk</email>
</author>
<published>2010-12-11T20:17:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e66a022a80d73b1a5d2e02c9db2c42e8b9853b40'/>
<id>urn:sha1:e66a022a80d73b1a5d2e02c9db2c42e8b9853b40</id>
<content type='text'>
FREQ is a ridiculously short name for a platform-specific macro in a
generic header, and it now conflicts with an enumeration in the
gspca/ov519 driver.

Also delete conditional reference to ixp4xx_get_board_tick_rate()
which is not defined anywhere.

Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Signed-off-by: Krzysztof Hałasa &lt;khc@pm.waw.pl&gt;
</content>
</entry>
<entry>
<title>Revert "Input: do not pass injected events back to the originating handler"</title>
<updated>2011-02-03T07:04:27Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2011-02-03T07:04:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9ae4345a46bdb148e32a547e89ff29563a11e127'/>
<id>urn:sha1:9ae4345a46bdb148e32a547e89ff29563a11e127</id>
<content type='text'>
This reverts commit 5fdbe44d033d059cc56c2803e6b4dbd8cb4e5e39.

Apparently there exist userspace programs that expect to be able to
"loop back" and distribute to readers events written into
/dev/input/eventX and this change made for the benefit of SysRq
handler broke them. Now that SysRq uses alternative method to suppress
filtering of the events it re-injects we can safely revert this change.

Reported-by: Kristen Carlson Accardi &lt;kristen@linux.intel.com&gt;
Cc: stable@kernel.org
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
</content>
</entry>
</feed>
