1. 23 4月, 2015 1 次提交
  2. 02 4月, 2015 4 次提交
  3. 18 3月, 2015 1 次提交
  4. 17 3月, 2015 1 次提交
    • B
      HID: wacom: ask for a in-prox report when it was missed · 5fcad167
      Benjamin Tissoires 提交于
      If noone listens to the input device when a tool comes in proximity,
      the tablet does not send the in-prox event when a client becomes available.
      That means that no events will be sent until the tool is taken out of
      proximity.
      
      In this situation, ask for the report WACOM_REPORT_INTUOSREAD which will
      read the corresponding feature and generate an in-prox event.
      To make some generation of hardware working, we need to unset the
      quirk NO_GET set by hid-core because the interfaces are seen as "boot
      mouse".
      
      We don't schedule this read in a worker while we are in an IO interrupt.
      We know that usbhid will do it asynchronously. If this is triggered by
      uhid, then this is obviously a client side bug :)
      Signed-off-by: NBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Acked-by: NJason Gerecke <killertofu@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      5fcad167
  5. 12 3月, 2015 1 次提交
    • J
      HID: wacom: Add battery presence indicator to wireless tablets · 71fa641e
      Jason Gerecke 提交于
      Declare the POWER_SUPPLY_PROP_PRESENT property to provide userspace
      with a way to determine if the battery on a wireless tablet is plugged
      in. Although current wireless tablets do not explicitly report this
      information, it can be inferred from other state information. In
      particular, a battery is assumed to be present if any of the following
      are true: a non-zero battery level reported, the battery is reported as
      charging, or the tablet is operating wirelessly.
      
      Note: The last condition above may not strictly hold for the Graphire
      Wireless (it charges from a DC barrel jack instead of a USB port), but I
      do not know what is reported in the no-battery condition.
      Signed-off-by: NJason Gerecke <killertofu@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      71fa641e
  6. 11 3月, 2015 5 次提交
  7. 03 3月, 2015 2 次提交
  8. 27 2月, 2015 1 次提交
    • B
      HID: wacom: add full support of the Wacom Bamboo PAD · 8c97a765
      Benjamin Tissoires 提交于
      The stylus of this device works just fine out of the box.
      The touch is seen by default as a mouse with relative events and some
      gestures.
      The wireless and the wired version have slightly different firmwares, but
      the debug mode 2 on the feature 2 is common to the 2 devices. In this mode,
      all the reports are emitted through the debug interface (pen, raw touch
      and mouse emulation), so we have to re-route manually the events.
      
      We keep the Pen interface as a HID_GENERIC one because it works, and only
      parse the raw touches while discarding the mouse emulation & gestures.
      
      Switching the default in raw mode allows us to have a consistent user
      experience accross all the multitouch touchpads (and enable the touch part
      of the devices).
      
      Note that the buttons of this devices are reported through the touch
      interface. There is no 'Pad' interface. It seemed more natural to have
      the BTN_LEFT and BTN_RIGHT reported with the touch because they are
      placed under the touch interface and it looks like they belong to the
      touch part.
      Tested-by: NJosep Sanchez Ferreres <josep.sanchez.ferreres@est.fib.upc.edu>
      Signed-off-by: NBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Acked-by: NPing Cheng <pingc@wacom.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      8c97a765
  9. 24 2月, 2015 1 次提交
  10. 19 2月, 2015 1 次提交
  11. 12 2月, 2015 1 次提交
  12. 29 1月, 2015 3 次提交
  13. 23 1月, 2015 1 次提交
  14. 12 1月, 2015 2 次提交
  15. 06 1月, 2015 1 次提交
  16. 12 12月, 2014 1 次提交
  17. 10 12月, 2014 1 次提交
  18. 06 12月, 2014 2 次提交
  19. 02 12月, 2014 2 次提交
  20. 27 11月, 2014 1 次提交
  21. 22 11月, 2014 2 次提交
    • J
      HID: wacom: Add angular resolution data to some ABS axes · 26fe4124
      Jason Gerecke 提交于
      Provide the resolution of several angular axes (tilt, pen rotation, puck
      rotation) to userspace. Because these values are natively degree-based, we
      need to convert them to into units/radian as required by the input_absinfo
      struct. To ensure wraparound behaves properly for the rotation axes, the
      converted value was rounded up rather than rounded nearest.
      
      Notably, the touchring axes (ABS_WHEEL and ABS_THROTTLE) are left without a
      a declared resolution because the their low resolution cannot be accurately
      represented (the worst-case rounding-induced error would be ~16 degrees).
      Pre-scaling the values and range by at least 10x would reduce the error in
      the resolution to acceptable levels, but the xf86-input-wacom driver is not
      able to use pre-scaled values for these axes at this time.
      Signed-off-by: NJason Gerecke <killertofu@gmail.com>
      Reviewed-by: NPing Cheng <pingc@wacom.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      26fe4124
    • J
      HID: wacom: Report ABS_TILT_{X,Y} as signed values · ec5fc1c1
      Jason Gerecke 提交于
      Centers the ABS_TILT_{X,Y} axes so that a value of zero is reported when
      the pen is vertical. Combined with resolution information in the next
      patch, this makes it possible for userspace to calculate the pen angle
      without needing hardware-specific knowledge. The xf86-input-wacom driver
      was updated to support signed tilt values in late-2012 (2f2acec).
      Signed-off-by: NJason Gerecke <killertofu@gmail.com>
      Reviewed-by: NPing Cheng <pingc@wacom.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      ec5fc1c1
  22. 21 11月, 2014 3 次提交
  23. 12 11月, 2014 1 次提交
  24. 07 11月, 2014 1 次提交