linux.git/drivers/input/touchscreen/usbtouchscreen.c, branch v3.17

Input: delete non-required instances of include

2014-01-07T07:23:57+00:00

None of these files are actually using any __init type directives
and hence don't need to include .  Most are just a
left over from __devinit and __cpuinit removal, or simply due to
code getting copied from one driver to the next.

Signed-off-by: Paul Gortmaker 
Signed-off-by: Dmitry Torokhov

Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

2013-12-09T17:28:31+00:00

Pull input updates from Dmitry Torokhov:
 "An update to ALPS to support devices on Dell XT2 (hopefully working
  better this time around and although it is largish it should not
  affect any other ALPS devices) and a tiny update to Elantech driver to
  support newer devices as well.

  Also a coupe of new input event codes have been defined"

* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
  Input: ALPS - add support for DualPoint device on Dell XT2 model
  Input: elantech - add support for newer (August 2013) devices
  Input: add SW_MUTE_DEVICE switch definition
  Input: usbtouchscreen - separate report and transmit buffer size handling
  Input: sur40 - suppress false uninitialized variable warning
  Input: add key code for ambient light sensor button
  Input: keyboard - "keycode & KEY_MAX" changes some keycode values

Input: usbtouchscreen - separate report and transmit buffer size handling

2013-12-02T06:18:04+00:00

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 
Signed-off-by: Dmitry Torokhov

Input: usbtouchscreen: ignore eGalax/D-Wav/EETI HIDs

2013-11-11T10:19:26+00:00

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

Signed-off-by: Forest Bond 
Acked-by: Dmitry Torokhov 
Signed-off-by: Jiri Kosina

Input: usbtouchscreen - initialize eGalax devices

2012-09-05T05:17:56+00:00

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 
Signed-off-by: Dmitry Torokhov

USB: input: usbtouchscreen.c: fix up dev_* messages

2012-05-04T22:33:16+00:00

Previously I had made the struct device point to the input device, but
after talking with Dmitry, he said that the USB device would make more
sense for this driver to point to.  So converted it to use that instead.

CC: Dmitry Torokhov 
CC: Henrik Rydberg 
CC: Rusty Russell 
CC: Viresh Kumar 
CC: Armando Visconti 
Signed-off-by: Greg Kroah-Hartman

USB: usbtouchscreen.c: remove dbg() usage

2012-05-02T04:33:23+00:00

dbg() was a very old USB-specific macro that should no longer
be used. This patch removes it from being used in the driver
and uses dev_dbg() instead.

CC: Dmitry Torokhov 
CC: Henrik Rydberg 
CC: Rusty Russell 
CC: Viresh Kumar 
CC: Armando Visconti 
Signed-off-by: Greg Kroah-Hartman

USB: input: usbtouchscreen.c: fix up dev_err() usage

2012-05-02T00:57:11+00:00

We should always reference the input device for dev_err(), not the USB
device.  Fix up the places where I got this wrong.

Reported-by: Dmitry Torokhov 
CC: Henrik Rydberg 
CC: Rusty Russell 
CC: Viresh Kumar 
CC: Armando Visconti 
Signed-off-by: Greg Kroah-Hartman

USB: usbtouchscreen.c: remove err() usage

2012-04-25T21:48:46+00:00

err() was a very old USB-specific macro that I thought had
gone away.  This patch removes it from being used in the
driver and uses dev_err() instead.

CC: Dmitry Torokhov 
CC: Henrik Rydberg 
CC: Rusty Russell 
CC: Viresh Kumar 
CC: Armando Visconti 
Signed-off-by: Greg Kroah-Hartman

Merge commit 'v3.3-rc6' into next

2012-03-09T18:55:17+00:00