05 Jan, 2012

2 commits


02 Jan, 2012

1 commit


19 Dec, 2011

1 commit


17 Dec, 2011

1 commit

  • ppc6xx_defconfig reveals this:

    drivers/built-in.o: In function `hidinput_cleanup_battery': drivers/hid/hid-input.c:351: undefined reference to`power_supply_unregister'
    drivers/built-in.o: In function `hidinput_setup_battery': drivers/hid/hid-input.c:338: undefined reference to `power_supply_register'
    make[1]: *** [.tmp_vmlinux1] Error 1

    The defconfig in question doens't mention either option and kbuild is
    genertaing

    CONFIG_HID_BATTERY_STRENGTH=y
    CONFIG_POWER_SUPPLY=m

    which is wrong. Put a proper dependency in place.

    Reported-by: Tony Breeds
    Signed-off-by: Jiri Kosina

    Jiri Kosina
     

15 Dec, 2011

1 commit


12 Dec, 2011

1 commit


06 Dec, 2011

1 commit


30 Nov, 2011

1 commit


28 Nov, 2011

1 commit

  • Some HID devices, such as my Bluetooth mouse, report their battery
    strength as an event. Rather than passing it through as a strange
    absolute input event, this patch registers it with the power_supply
    subsystem as a battery, so that the device's Battery Strength can be
    reported to usermode.

    The battery appears in sysfs names
    /sys/class/power_supply/hid--battery, and it is a child of the
    battery-containing device, so it should be clear what it's the battery of.

    Unfortunately on my current Fedora 16 system, while the battery does
    appear in the UI, it is listed as a Laptop Battery with 0% charge (since
    it ignores the "capacity" property of the battery and instead computes
    it from the "energy*" fields, which we can't supply given the limited
    information contained within the HID Report).

    Still, this patch is the first step.

    Signed-off-by: Jeremy Fitzhardinge
    Signed-off-by: Jiri Kosina

    Jeremy Fitzhardinge
     

23 Nov, 2011

3 commits

  • 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: David Herrmann
    Signed-off-by: Jiri Kosina

    David Herrmann
     
  • 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: Jiri Kosina

    Jiri Kosina
     
  • 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: K. Y. Srinivasan
    Signed-off-by: Jiri Kosina

    K. Y. Srinivasan
     

25 Oct, 2011

2 commits


21 Oct, 2011

1 commit

  • Support the following models: Super Joy Box 3 Pro, Super Dual Box Pro
    and Super Joy Box 5 Pro. These models have support for pressure
    sensitive buttons and they can force the controller to either digital
    or analog mode, both of which are not supported yet.

    Signed-off-by: Sean Young
    Signed-off-by: Jiri Kosina

    Sean Young
     

17 Oct, 2011

2 commits

  • Remove Kconfig dependency for hid-primax driver on CONFIG_EXPERT.
    Please see changelog of 73d5e8f77e8 ("HID: fix up 'EMBEDDED' mess in
    Kconfig") for reasoning behind this.

    Signed-off-by: Jiri Kosina

    Jiri Kosina
     
  • 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: Terry Lambert
    Signed-off-by: Jiri Kosina

    Terry Lambert
     

15 Sep, 2011

1 commit

  • With this driver, all the devices paired to a single Unifying
    receiver are exposed to user processes in separated /input/dev
    nodes.

    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: Nestor Lopez Casado
    Signed-off-by: Benjamin Tissoires
    Signed-off-by: Jiri Kosina

    Nestor Lopez Casado
     

07 Sep, 2011

1 commit


23 Aug, 2011

1 commit


16 Aug, 2011

1 commit


11 Aug, 2011

1 commit


04 Aug, 2011

2 commits


23 Jul, 2011

1 commit


21 Jul, 2011

1 commit


11 Jul, 2011

1 commit


27 Jun, 2011

1 commit

  • Add force feedback support for Holtek On Line Grip based HID devices.

    The protocol is more complex than that of most other rumblepads, but the
    device still needs to be handled as a memoryless one.

    Tested by Cleber de Mattos Casali with a 1241:5015 "Clone Joypad Super
    Power Fire" gamepad, with help from Hendrik Iben .

    Signed-off-by: Anssi Hannula
    Tested-by: Cleber de Mattos Casali
    Signed-off-by: Jiri Kosina

    Anssi Hannula
     

13 Jun, 2011

1 commit


08 Jun, 2011

1 commit

  • 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: Stefan Kriwanek
    Signed-off-by: Jiri Kosina

    Stefan Kriwanek
     

07 Jun, 2011

1 commit


23 May, 2011

2 commits


20 May, 2011

5 commits


19 May, 2011

1 commit