summaryrefslogtreecommitdiffstats
path: root/net/lapb
diff options
context:
space:
mode:
authorForest Bond <forest.bond@rapidrollout.com>2012-09-04 20:27:37 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2012-09-04 22:17:56 -0700
commit037a833ed05a86d01ea27a2c32043b86c549be1b (patch)
treef8350bd3b8f43218374342544a1427d1e66a9bb7 /net/lapb
parent6f4d0382e2a6d27045e223d8c452659477826650 (diff)
downloadtalos-obmc-linux-037a833ed05a86d01ea27a2c32043b86c549be1b.tar.gz
talos-obmc-linux-037a833ed05a86d01ea27a2c32043b86c549be1b.zip
Input: usbtouchscreen - initialize eGalax devices
Certain eGalax devices expose an interface with class HID and protocol None. Some work with usbhid and some work with usbtouchscreen, but there is no easy way to differentiate. Sending an eGalax diagnostic packet seems to kick them all into using the right protocol for usbtouchscreen, so we can continue to bind them all there (as opposed to handing some off to usbhid). This fixes a regression for devices that were claimed by (and worked with) usbhid prior to commit 139ebe8dc80dd74cb2ac9f5603d18fbf5cff049f ("Input: usbtouchscreen - fix eGalax HID ignoring"), which made usbtouchscreen claim them instead. With this patch they will still be claimed by usbtouchscreen, but they will actually report events usbtouchscreen can understand. Note that these devices will be limited to the usbtouchscreen feature set so e.g. dual touch features are not supported. I have the distinct pleasure of needing to support devices of both types and have tested accordingly. Signed-off-by: Forest Bond <forest.bond@rapidrollout.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'net/lapb')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud