1. 28 May, 2013 1 commit
    • Jiri Slaby's avatar
      HID: add driver for ELO 4000/4500 · d23efc19
      Jiri Slaby authored
      This is a driver for ELO 4000/4500 devices which report themselves as
      HID devices, but do not really send HID events on touch. So we
      introduce a new HID 'quirk' driver with a raw_event handler where we
      take care of those events.
      What we need additionally is an input_configured hook, because the
      device does not mention anything about PRESSURE and TOUCH in its
      report descriptor, but it actually generate those. So we set the bits
      in the corresponding input_dev in that hook.
      Thanks to Petr Ostadal who was willing to test the driver. The rest of
      Cc's listed below had something to do with that driver over the years
      in our enterprise tree.
      Signed-off-by: default avatarJiri Slaby <jslaby@suse.cz>
      Tested-by: default avatarPetr Ostadal <postadal@suse.cz>
      Cc: Oliver Neukum <oliver@neukum.org>
      Cc: Vojtech Pavlik <vojtech@suse.cz>
      Cc: Egbert Eich <eich@suse.com>
      Cc: Libor Pechacek <lpechacek@suse.cz>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  2. 19 Apr, 2013 1 commit
  3. 14 Mar, 2013 1 commit
  4. 19 Feb, 2013 1 commit
    • Vivien Didelot's avatar
      HID: add ThingM blink(1) USB RGB LED support · 30ba2fbd
      Vivien Didelot authored
      The ThingM blink(1) is an open source hardware USB RGB LED. It contains
      an internal EEPROM, allowing to configure up to 12 light patterns. A
      light pattern is a RGB color plus a fade time. This driver registers a
      LED class instance with additional sysfs attributes to support basic
      functions such as setting RGB colors, fade and playing. Other functions
      are still accessible through the hidraw interface.
      At this time, the only documentation for the device is the firmware
      source code from ThingM, plus a few schematics. They are available at:
      This patch is version 3. It updates the name of the source file, the
      driver and the led sysfs entry, according to comments from Jiri Kosina
      and Simon Wood.
      Signed-off-by: default avatarVivien Didelot <vivien.didelot@savoirfairelinux.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  5. 31 Jan, 2013 2 commits
  6. 19 Nov, 2012 1 commit
  7. 31 Oct, 2012 1 commit
  8. 17 Oct, 2012 1 commit
  9. 01 Oct, 2012 1 commit
  10. 06 Sep, 2012 1 commit
  11. 15 Aug, 2012 1 commit
  12. 12 Jul, 2012 1 commit
  13. 28 Jun, 2012 1 commit
  14. 18 Jun, 2012 1 commit
  15. 08 Jun, 2012 1 commit
  16. 01 May, 2012 1 commit
  17. 13 Apr, 2012 1 commit
  18. 22 Feb, 2012 1 commit
  19. 06 Feb, 2012 1 commit
    • Jarod Wilson's avatar
      HID: add support for tivo slide remote · 44ea35c1
      Jarod Wilson authored
      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
      CC: Jiri Kosina <jkosina@suse.cz>
      Signed-off-by: default avatarJarod Wilson <jarod@redhat.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  20. 05 Feb, 2012 1 commit
  21. 06 Dec, 2011 1 commit
  22. 30 Nov, 2011 1 commit
  23. 22 Nov, 2011 5 commits
    • David Herrmann's avatar
      HID: wiimote: Add debugfs support stubs · 43e5e7c6
      David Herrmann authored
      Add initializer and deinitializer for debugfs support. This will later allow raw
      eeprom access and direct DRM modifications to debug wiimote behaviour and
      further protocol reverse-engineerings.
      Signed-off-by: default avatarDavid Herrmann <dh.herrmann@googlemail.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
    • David Herrmann's avatar
      HID: wiimote: Add extension support stub · cb99221b
      David Herrmann authored
      The wiimote supports several extensions. This adds a separate source file which
      handles all extensions and can be disabled at compile-time.
      The driver reacts on "plug"-events on the extension port and starts a worker
      which initializes or deinitializes the extensions.
      Currently, the initialization logic is not fully understood and we can only
      detect and enable all extensions when all extensions are deactivated. Therefore,
      we need to disable all extensions, then detect and activate them again to react
      on "plug"-events.
      However, deactivating extensions will generate a new "plug"-event and we will
      never leave that loop. Hence, we only support extensions if they are plugged
      before the wiimote is connected (or before the ext-input device is opened). In
      the future we may support full extension hotplug support, but
      reverse-engineering this may take a while.
      Signed-off-by: default avatarDavid Herrmann <dh.herrmann@googlemail.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
    • David Herrmann's avatar
      HID: wiimote: Rename driver to allow multiple source files · 192a1acf
      David Herrmann authored
      Extension and sound support for the wiimote are quite complex and will be
      implemented in separate source files. Hence rename the current driver to "-core"
      suffix so multiple files can be linked into this module.
      Signed-off-by: default avatarDavid Herrmann <dh.herrmann@googlemail.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
    • Jiri Kosina's avatar
      HID: hyperv: fixup Kconfig / Makefile entries · 6cf851d8
      Jiri Kosina authored
      Rename the Kconfig entry for hyperv mouse driver so that it has
      HID_ prefix as all the other drivers; while at it, place the entry
      for this driver to properly ordered place in Makefile and Kconfig.
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
    • K. Y. Srinivasan's avatar
      HID: Move the hid-hyperv driver out of staging · b95f5bcb
      K. Y. Srinivasan authored
      The file  hid-hyperv.c implements a hid compliant mouse driver for use on a
      Hyper-V based system. This driver is currently in the staging area and as part
      of the effort to move this driver out of staging, I had posted the driver code
      for community review a few weeks ago. This current patch addresses all the
      review comments I have gotten to date. All the relevant patches have already
      been submitted to the staging tree as well.
      As per Greg's suggestion, this patch does not get rid of the code from
      the staging area. Once the mouse driver lands under the hid directory,
      we will cleanup the staging directory.
      Signed-off-by: default avatarK. Y. Srinivasan <kys@microsoft.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  24. 17 Oct, 2011 1 commit
    • Terry Lambert's avatar
      HID: support primax keyboards violating USB HID spec · f6a04605
      Terry Lambert authored
      Primax keyboards with the issue this driver addresses report modifier
      keys as in band key events instead of as out of band modifier bits,
      resulting in the modifier keys generating key up events immediately
      before the keys they are intended to modify.  This driver rewrites
      the raw report data from such keyboards into USB HID 1.11 compliant
      report data.  It only matches the USB vendor and product IDs for the
      keyboard it has been tested on. Since there are several keyboards,
      notably a number of laptops and folding USB keyboards known to have
      similar unresolved problem reports, the list is expected to grow.
      Signed-off-by: default avatarTerry Lambert <tlambert@chromium.org>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  25. 15 Sep, 2011 1 commit
    • Nestor Lopez Casado's avatar
      HID: Add full support for Logitech Unifying receivers · 534a7b8e
      Nestor Lopez Casado authored
      With this driver, all the devices paired to a single Unifying
      receiver are exposed to user processes in separated /input/dev
      Keyboards with different layouts can be treated differently,
      Multiplayer games on single PC (like home theater PC) can
      differentiate input coming from different kbds paired to the
      same receiver.
      Up to now, when Logitech Unifying receivers are connected to a
      Linux based system, a single keyboard and a single mouse are
      presented to the HID Layer, even if the Unifying receiver can
      pair up to six compatible devices. The Unifying receiver by default
      multiplexes all incoming events (from multiple keyboards/mice)
      into these two.
      Signed-off-by: default avatarNestor Lopez Casado <nlopezcasad@logitech.com>
      Signed-off-by: default avatarBenjamin Tissoires <benjamin.tissoires@gmail.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  26. 04 Aug, 2011 1 commit
  27. 11 Jul, 2011 1 commit
  28. 27 Jun, 2011 1 commit
  29. 08 Jun, 2011 1 commit
    • Stefan Kriwanek's avatar
      HID: Add driver to fix Speedlink VAD Cezanne support · 74bc6953
      Stefan Kriwanek authored
      Speedlink VAD Cezanne have a hardware bug that makes the cursor "jump" from one
      place to another every now and then. The issue are relative motion events
      erroneously reported by the device, each having a distance value of +256. This
      256 can in fact never occur due to real motion, therefore those events can
      safely be ignored.  The driver also drops useless EV_REL events with a value of
      0, that the device sends every time it sends an "real" EV_REL or EV_KEY event.
      Signed-off-by: default avatarStefan Kriwanek <mail@stefankriwanek.de>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  30. 22 Apr, 2011 1 commit
  31. 24 Mar, 2011 1 commit
  32. 21 Mar, 2011 2 commits
  33. 14 Mar, 2011 1 commit
  34. 12 Mar, 2011 1 commit