1. 23 7月, 2012 1 次提交
  2. 22 7月, 2012 1 次提交
  3. 20 7月, 2012 2 次提交
    • D
      HID: Allow drivers to be their own listener · 4bc19f62
      David Herrmann 提交于
      hid-picolcd and hid-wiimote do not allow any of hidinput, hiddev or hidraw
      to claim the device but still want to remain on the bus. Hence, if a
      driver uses the raw_event callback but no other listener claimed the
      device, we still leave it on the bus as the driver handles everything by
      itself. It thus becomes its own listener.
      
      Under some circumstances (eg., hidinput_connect() fails and raw_event set)
      a device may be left on the bus even though it requires external
      listeners. But then if hidinput_connect() fails there are bigger issues
      than a device that is left unhandled. So we can safely use this heuristic
      to avoid adding another flag for special devices like hid-picolcd and
      hid-wiimote.
      
      This also removes the ugly hack from hid-picolcd as this is no longer
      required.
      Signed-off-by: NDavid Herrmann <dh.herrmann@googlemail.com>
      Acked-by: NHenrik Rydberg <rydberg@euromail.se>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      4bc19f62
    • M
      HID: hid-core: optimize in case of hidraw · b94e3c94
      Matthieu CASTET 提交于
      When using hidraw, hid buffer can be big and take lot's of
      time to process (interrupt) kernel context.
      Don't try to parse report if we are only interrested in hidraw.
      
      Also don't prepare data for debug stuff if no debugfs file
      are opened.
      Signed-off-by: NMatthieu CASTET <matthieu.castet@parrot.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      b94e3c94
  4. 12 7月, 2012 1 次提交
  5. 11 7月, 2012 2 次提交
  6. 28 6月, 2012 1 次提交
  7. 12 6月, 2012 1 次提交
  8. 08 6月, 2012 1 次提交
  9. 15 5月, 2012 1 次提交
  10. 14 5月, 2012 2 次提交
  11. 01 5月, 2012 6 次提交
  12. 28 4月, 2012 1 次提交
  13. 20 4月, 2012 1 次提交
  14. 14 4月, 2012 1 次提交
  15. 28 3月, 2012 1 次提交
  16. 20 3月, 2012 1 次提交
    • A
      HID: multitouch: add PID for Fructel product · 4d5df5d1
      Andreas Nielsen 提交于
      Adds multitouch support for the Gametel Android game controller.
      
      The multitouch events are emulated by the Gametel device. Each physical button
      is configured to generate a MT event on a specific coordinate. This seems to be
      the only way for us to support Android games that doesn't support HID gamepads.
      It is possible to inject MT events at Android level, but this requires root on
      the phone.
      Signed-off-by: NAndreas Nielsen <eas@svep.se>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      4d5df5d1
  17. 13 3月, 2012 1 次提交
  18. 12 3月, 2012 1 次提交
  19. 09 3月, 2012 1 次提交
  20. 06 3月, 2012 2 次提交
  21. 28 2月, 2012 1 次提交
  22. 22 2月, 2012 1 次提交
  23. 21 2月, 2012 3 次提交
  24. 15 2月, 2012 1 次提交
  25. 07 2月, 2012 2 次提交
    • N
      HID: waltop: Add support for Waltop Q Pad · 4fdc18d1
      Nikolai Kondrashov 提交于
      Add support for Waltop Q Pad by fixing its report descriptor.
      
      This tablet is also sold as Aiptek HyperPen Mini. Other possible names
      include: NGS Flexi Style, VisTablet PenPad, iVistaTablet Q Flex Pad, Bravod
      Q-PD65-S.
      Signed-off-by: NNikolai Kondrashov <spbnick@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      4fdc18d1
    • J
      HID: add support for tivo slide remote · 44ea35c1
      Jarod Wilson 提交于
      This patch finishes off adding full support for the TiVo Slide remote,
      which is a mostly pure HID device from the perspective of the kernel.
      There are a few mappings that use a vendor-specific usage page, and a
      few keys in the consumer usage page that I think make sense to remap
      slightly, to better fit their key labels' intended use. Doing this in a
      stand-alone hid-tivo.c makes the modifications only matter for this
      specific device.
      
      What's actually connected to the computer is a Broadcom-made usb dongle,
      which has an embedded hub, bluetooth adapter, mouse and keyboard
      devices. You pair with the dongle, then the remote sends data that its
      converted into HID on the keyboard interface (the mouse interface
      doesn't do anything interesting, so far as I can tell).
      
      lsusb for this device:
      Bus 004 Device 005: ID 0a5c:2190 Broadcom Corp.
      Bus 004 Device 004: ID 0a5c:4503 Broadcom Corp.
      Bus 004 Device 003: ID 150a:1201
      Bus 004 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
      
      Speaking of the keyboard interface, the remote actually does contain a
      keyboard as well. The top slides away, revealing a reasonably functional
      qwerty keyboard (not unlike many slide cell phones), thus the product
      name.
      
      CC: Jiri Kosina <jkosina@suse.cz>
      Signed-off-by: NJarod Wilson <jarod@redhat.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      44ea35c1
  26. 03 2月, 2012 1 次提交
  27. 02 2月, 2012 1 次提交
  28. 25 1月, 2012 1 次提交
    • A
      Dynamic ID addition doesn't need get_driver() · cef9bc56
      Alan Stern 提交于
      As part of the removal of get_driver()/put_driver(), this patch
      (as1511) changes all the places that add dynamic IDs for drivers.
      Since these additions are done by writing to the drivers' sysfs
      attribute files, and the attributes are removed when the drivers are
      unregistered, there is no reason to take an extra reference to the
      drivers.
      
      The one exception is the pci-stub driver, which calls pci_add_dynid()
      as part of its registration.  But again, there's no reason to take an
      extra reference here, because the driver can't be unloaded while it is
      being registered.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      CC: Dmitry Torokhov <dmitry.torokhov@gmail.com>
      CC: Jiri Kosina <jkosina@suse.cz>
      CC: Jesse Barnes <jbarnes@virtuousgeek.org>
      CC: Dominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      cef9bc56