Home
last modified time | relevance | path

Searched hist:"2 a6cdbdd4cc0da0b0190b9a43648dff7b44adc0a" (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/drivers/hid/
H A Dwacom_wac.hdiff 2a6cdbdd4cc0da0b0190b9a43648dff7b44adc0a Mon Jun 15 20:01:45 CDT 2015 Jason Gerecke <killertofu@gmail.com> HID: wacom: Introduce new 'touch_input' device

Instead of having a single 'input_dev' device that will take either pen
or touch data depending on the type of the device, create seperate devices
devices for each. By splitting things like this, we can support devices
(e.g. the I2C "AES" sensors in some newer tablet PCs) that send both pen
and touch reports from a single endpoint.

Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
H A Dwacom_sys.cdiff 2a6cdbdd4cc0da0b0190b9a43648dff7b44adc0a Mon Jun 15 20:01:45 CDT 2015 Jason Gerecke <killertofu@gmail.com> HID: wacom: Introduce new 'touch_input' device

Instead of having a single 'input_dev' device that will take either pen
or touch data depending on the type of the device, create seperate devices
devices for each. By splitting things like this, we can support devices
(e.g. the I2C "AES" sensors in some newer tablet PCs) that send both pen
and touch reports from a single endpoint.

Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
H A Dwacom_wac.cdiff 2a6cdbdd4cc0da0b0190b9a43648dff7b44adc0a Mon Jun 15 20:01:45 CDT 2015 Jason Gerecke <killertofu@gmail.com> HID: wacom: Introduce new 'touch_input' device

Instead of having a single 'input_dev' device that will take either pen
or touch data depending on the type of the device, create seperate devices
devices for each. By splitting things like this, we can support devices
(e.g. the I2C "AES" sensors in some newer tablet PCs) that send both pen
and touch reports from a single endpoint.

Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>