From: Benjamin Tissoires <hidden> Date: 2015-06-18 19:58:53
As mentioned in the comment in the code, both the pen and touch data
come from the interface tagged as BAMBOO_PAD. The driver re-routes the
events for the Pen to the generic HID interface and keeps the ones for
the touch through this current interface.
Clearing the WACOM_DEVICETYPE_PEN bit removes the extra unused interface
and makes the Bamboo PAD to behave like in 4.1.
Signed-off-by: Benjamin Tissoires <redacted>
---
Hi,
well, the fix was definitively easy to restore the Bamboo PAD interface.
Thanks Jason for the good cleanup and sorry for not having the time to review
the previous series.
Cheers,
Benjamin
drivers/hid/wacom_wac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Jason Gerecke <hidden> Date: 2015-06-19 16:06:11
On 6/18/2015 12:58 PM, Benjamin Tissoires wrote:
quoted hunk
As mentioned in the comment in the code, both the pen and touch data
come from the interface tagged as BAMBOO_PAD. The driver re-routes the
events for the Pen to the generic HID interface and keeps the ones for
the touch through this current interface.
Clearing the WACOM_DEVICETYPE_PEN bit removes the extra unused interface
and makes the Bamboo PAD to behave like in 4.1.
Signed-off-by: Benjamin Tissoires <redacted>
---
Hi,
well, the fix was definitively easy to restore the Bamboo PAD interface.
Thanks Jason for the good cleanup and sorry for not having the time to review
the previous series.
Cheers,
Benjamin
drivers/hid/wacom_wac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Nit: Looks like I forgot to update this comment to say
WACOM_DEVICETYPE_TOUCH. Mind fixing that in this patch since you're here
anyway?
Otherwise, looks good :)
Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com>
--
Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....
*/
if (features->type == BAMBOO_PAD)
- features->device_type |= WACOM_DEVICETYPE_TOUCH;
+ features->device_type = WACOM_DEVICETYPE_TOUCH;
if (wacom->hdev->bus == BUS_BLUETOOTH)
features->quirks |= WACOM_QUIRK_BATTERY;
As mentioned in the comment in the code, both the pen and touch data
come from the interface tagged as BAMBOO_PAD. The driver re-routes the
events for the Pen to the generic HID interface and keeps the ones for
the touch through this current interface.
Clearing the WACOM_DEVICETYPE_PEN bit removes the extra unused interface
and makes the Bamboo PAD to behave like in 4.1.
Signed-off-by: Benjamin Tissoires <redacted>
Could you please be a little bit more specific about which commit this is
a bugfix for?
Thanks a lot.
--
Jiri Kosina
SUSE Labs
From: Benjamin Tissoires <hidden> Date: 2015-07-07 14:04:18
On Jun 29 2015 or thereabouts, Jiri Kosina wrote:
On Thu, 18 Jun 2015, Benjamin Tissoires wrote:
quoted
As mentioned in the comment in the code, both the pen and touch data
come from the interface tagged as BAMBOO_PAD. The driver re-routes the
events for the Pen to the generic HID interface and keeps the ones for
the touch through this current interface.
Clearing the WACOM_DEVICETYPE_PEN bit removes the extra unused interface
and makes the Bamboo PAD to behave like in 4.1.
Signed-off-by: Benjamin Tissoires <redacted>
Could you please be a little bit more specific about which commit this is
a bugfix for?
Jason, Jiri,
OK, I will amend the patch and send a v2 this week (Thursday maybe when
I get my hand on the Bamboo PAD).
Cheers,
Benjamin