Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 04 9月, 2014 3 次提交
    • C
      HID: add support for PenMount HID TouchScreen Driver · ffe51d0d
      由 Christian Gmeiner 提交于 
      This patch adds a seperate hid-penmount driver to work
around an issue with the HID report descriptor. The
descriptor does not contain the ContactID usage and as
result the touchscreen is represented as normal mouse
to the system.

This driver maps the button 0 emitted by the touchscreen
to BTN_TOUCH. This makes it possible to use touch events
in userspace.
Signed-off-by: NChristian Gmeiner <christian.gmeiner@gmail.com>
Reviewed-by: NBenjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      ffe51d0d
    • J
      HID: thingm: fix workqueue race on remove · 67a97845
      由 Jiri Kosina 提交于 
      thingm_remove_rgb() needs to flush the workqueue after all the LED classes
have been unregistered, otherwise the removal might race with another LED
event coming, causing thingm_led_set() to schedule additional work after
thingm_remove_rgb() has flushed it. This obviously causes oops later, as
the scheduled work has been freed in the meantime.

In addition to that, move the hid_hw_stop() to an earlier place, so that
dmesg is not polluted by failure messages about not being able to write
the LED while the device is being shut down.
Reported-and-tested-by: NDylan Alex Simon <dylan-kernel@dylex.net>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      67a97845
    • A
      HID: usbhid: improve handling of Clear-Halt and reset · 8f507ef5
      由 Alan Stern 提交于 
      This patch changes the way usbhid carries out Clear-Halt and reset.

Currently, after a Clear-Halt on the interrupt-IN endpoint, the driver
immediately restarts the interrupt URB, even if the Clear-Halt failed.
This doesn't work out well when the reason for the failure was that
the device was disconnected (when a low- or full-speed device is
connected through a hub to an EHCI controller, transfer errors caused
by disconnection are reported as stalls by the hub).  Instead now the
driver will attempt a reset after a failed Clear-Halt.

The way resets are carried out is also changed.  Now the driver will
call usb_queue_reset_device() instead of calling usb_reset_device()
directly.  This avoids a deadlock that would arise when a device is
unplugged: The hid_reset() routine runs as a workqueue item, a reset
attempt after the device has been unplugged will fail, failure will
cause usbhid to be unbound, and the disconnect routine will try to do
cancel_work_sync().  The usb_queue_reset_device() implementation is
carefully written to handle scenarios like this one properly.
Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      8f507ef5
  3. 26 8月, 2014 1 次提交
  5. 21 8月, 2014 3 次提交
  7. 15 8月, 2014 1 次提交
  9. 14 8月, 2014 1 次提交
  11. 13 8月, 2014 1 次提交
  13. 12 8月, 2014 3 次提交
  15. 07 8月, 2014 8 次提交
  17. 04 8月, 2014 1 次提交
  19. 30 7月, 2014 1 次提交
  21. 29 7月, 2014 17 次提交