linux.git/drivers/input/tablet/wacom.h, branch master

Input: wacom - move the USB (now hid) Wacom driver in drivers/hid

2014-07-26T01:55:38+00:00

wacom.ko is now a full HID driver, we have to move it into the proper
subdirectory: drivers/hid.

Signed-off-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov

Input: wacom - register the input devices on top of the HID one

2014-07-26T01:53:52+00:00

Matches the current behavior of the HID subsystem and removes one more
dependency over USB.

The current user space clients which relies on this to fetch the
LEDs path need an update. However, we already break them in the
kernel v3.11 for the Bluetooth Wacom devices. They are going to be fixed
soon.

Signed-off-by: Benjamin Tissoires 
Reviewed-by: Jason Gerecke 
Tested-by: Jason Gerecke 
Signed-off-by: Dmitry Torokhov

Input: wacom - switch from an USB driver to a HID driver

2014-07-26T01:53:50+00:00

All USB Wacom tablets are actually HID devices.
For historical reasons, they are handled as plain USB devices.
The current code makes more and more reference to the HID subsystem
like implementing its own HID report descriptor parser to handle new
devices.

From the user point of view, we can transparently switch from this state
to a driver handled in the HID subsystem and clean up a lot of USB specific
code in the wacom.ko driver.

The other benefit once the USB dependecies have been removed is that we can
use a tool like uhid to make regression tests and allow further cleanup or
new implementations without risking breaking current behaviors.

To match the current handling of devices in wacom_wac.c, we rely on the
hid_type set by usbhid. usbhid sets the hid_type to HID_TYPE_USBMOUSE when
it sees a USB boot mouse protocol declared and HID_TYPE_USBNONE when the
device is plain HID. There is thus a one to one matching between the list
of supported devices before and after the switch from USB to HID.

Signed-off-by: Benjamin Tissoires 
Reviewed-by: Jason Gerecke 
Tested-by: Jason Gerecke 
Signed-off-by: Dmitry Torokhov

Input: wacom - create a separate input device for pads

2014-07-26T01:53:46+00:00

Currently, the pad events are sent through the stylus input device
for the Intuos/Cintiqs, and through the touch input device for the
Bamboos.

To differentiate the buttons pressed on the pad from the ones pressed
on the stylus, the Intuos/Cintiq uses MISC_SERIAL and ABS_MISC. This
lead to a multiplexing of the events into one device, which are then
splitted out in xf86-input-wacom. Bamboos are not using MISC events
because the pad is attached to the touch interface, and only BTN_TOUCH
is used for the finger (and DOUBLE_TAP, etc...). However, the user space
driver still splits out the pad from the touch interface in the same
way it does for the pro line devices.

The other problem we can see with this fact is that some of the Intuos
and Cintiq have a wheel, and the effective range of the reported values
is [0..71]. Unfortunately, the airbrush stylus also sends wheel events
(there is a small wheel on it), but in the range [0..1023]. From the user
space point of view it is kind of difficult to understand that because
the wheel on the pad are quite common, while the airbrush tool is not.

A solution to fix all of these problems is to split out the pad device
from the stylus/touch. This decision makes more sense because the pad is
not linked to the absolute position of the finger or pen, and usually, the
events from the pad are filtered out by the compositor, which then convert
them into actions or keyboard shortcuts.

For backward compatibility with current xf86-input-wacom, the pad devices
still present the ABS_X, ABS_Y and ABS_MISC events, but they can be
completely ignored in the new implementation.

Signed-off-by: Benjamin Tissoires 
Reviewed-by: Ping Cheng 
Reviewed-by: Jason Gerecke 
Signed-off-by: Dmitry Torokhov

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

Input: wacom - add 0xE5 (MT device) support

2012-04-30T04:13:53+00:00

Main part of patch is adding support for a new Wacom MT touch
packet and labels these devices using MTSCREEN type.

Other items of interest:

Delete some duplicate code in HID parsing for Y info since
its already done in X path.

In wacom_query_tablet_data(), only invoke the set report
that requests tablets to send Wacom Touch packets for
Finger interfaces.  Mostly, this is to make code intent clear.

Tested-by: Jason Gerecke 
Signed-off-by: Chris Bagwell 
Signed-off-by: Ping Cheng 
Signed-off-by: Dmitry Torokhov

Input: wacom - wireless battery status

2012-03-26T06:33:17+00:00

Signed-off-by: Chris Bagwell 
Tested-by: Jason Gerecke 
Acked-by: Ping Cheng 
Signed-off-by: Dmitry Torokhov

Input: wacom - create inputs when wireless connect

2012-03-26T06:32:59+00:00

When a tablet connect or disconnect is detected, schedule
work queue to register or unregister related input devices.

When a wireless tablet connects, it reports same USB PID
used if tablet is connected with USB cable. Use this to
update features values, set input capabilities, and then
register device.  From there, the Pen and Touch interfaces
will reuse the existing tablet's IRQ routines.

Its possible that 1 receiver is shared with 2 tablets with
different PID (small and medium Bamboo for example) so the
input is unregister at disconnect to better support this case.

Signed-off-by: Chris Bagwell 
Tested-by: Jason Gerecke 
Acked-by: Ping Cheng 
Signed-off-by: Dmitry Torokhov

Input: wacom - add LED support for Cintiq 21ux2

2011-10-05T07:26:21+00:00

Cintiq 21ux2 has two sets of four LEDs on right and left side of
the tablet, respectively.

Reviewed-by: Eduard Hasenleithner 
Tested-by: Eduard Hasenleithner 
Signed-off-by: Ping Cheng 
Signed-off-by: Dmitry Torokhov

Input: wacom - don't expose LED inactive option

2011-10-05T07:26:17+00:00

The LED also indicates the status of the tablet. Don't turn it off.

Reviewed-by: Eduard Hasenleithner 
Tested-by: Eduard Hasenleithner 
Signed-off-by: Ping Cheng 
Signed-off-by: Dmitry Torokhov