Eric Lee / smarc-fsl-linux-kernel

09 Jan, 2012

1 commit

08 Jan, 2012

1 commit

05 Jan, 2012

2 commits

02 Jan, 2012

2 commits

15 Dec, 2011

1 commit

06 Dec, 2011

1 commit

30 Nov, 2011

2 commits

23 Nov, 2011

5 commits

14 Nov, 2011

1 commit

29 Oct, 2011

1 commit

28 Oct, 2011

1 commit

  • 213f9da80   HID: Add device IDs for Macbook Pro 8 keyboards ... Browse Code »
    1

    This patch adds keyboard support for Macbook Pro 8 models which has
    WELLSPRING5A model name and 0x0252, 0x0253 and 0x0254 USB IDs. Trackpad
    support for those models are added to bcm5974 in
    c331eb580a0a7906c0cdb8dbae3cfe99e3c0e555 ("Input: bcm5974 - Add
    support for newer MacBookPro8,2).

    Signed-off-by: Gökçen Eraslan
    Acked-by: Henrik Rydberg
    Signed-off-by: Jiri Kosina

    Gökçen Eraslan
     

25 Oct, 2011

2 commits

21 Oct, 2011

1 commit

  • 1bcc20675   HID: Add device IDs for more SJOY adapters ... Browse Code »

    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

1 commit

  • f6a04605f   HID: support primax keyboards violating USB HID spec ... Browse Code »

    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
     

03 Oct, 2011

1 commit

20 Sep, 2011

1 commit

  • a062cc5a7   HID: hid-multitouch: add support for the IDEACOM 6650 chip ... Browse Code »

    The IDEACOM 6650 multitouch chip, present in various all-in-one computers,
    uses the serial version of the HID multitouch protocol. No existing class
    supports this.

    In principle, the new MT_CLS_SERIAL should work for other
    serial panels as well, perhaps including some eGalax panels.

    Signed-off-by: Stephane Chatty
    Signed-off-by: Jiri Kosina

    Stephane Chatty
     

15 Sep, 2011

1 commit

  • 534a7b8e1   HID: Add full support for Logitech Unifying receivers ... Browse Code »
    43

    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
     

25 Aug, 2011

1 commit

23 Aug, 2011

1 commit

  • f5e428258   HID: usbhid: Add support for SiGma Micro chip ... Browse Code »
    1

    Patch to add SiGma Micro-based keyboards (1c4f:0002) to hid-quirks.

    These keyboards dont seem to allow the records to be initialized, and hence a
    timeout occurs when the usbhid driver attempts to initialize them. The patch
    just adds the signature for these keyboards to the hid-quirks list with the
    setting HID_QUIRK_NO_INIT_REPORTS. This removes the 5-10 second wait for the
    timeout to occur.

    Signed-off-by: Jeremiah Matthey
    Signed-off-by: Jiri Kosina

    Jeremiah Matthey
     

16 Aug, 2011

1 commit

10 Aug, 2011

1 commit

  • 5d922baa6   HID: add support for MacBookAir4,2 keyboard. ... Browse Code »
    1

    Added USB device IDs for MacBookAir4,2 keyboard. Device constants were
    copied from the MacBookAir3,2 constants. The 4,2 device specification is
    reportedly unchanged from the 3,2 predecessor and seems to work well.

    Signed-off-by: Joshua V Dillon
    Signed-off-by: Chase Douglas
    Signed-off-by: Jiri Kosina

    Joshua V. Dillon
     

04 Aug, 2011

1 commit

  • 7362cd228   HID: lg4ff - Move handling of Logitech wheels to lg4ff driver ... Browse Code »

    This is the first out of five patches me and Simon Wood (CC'd) have been
    working on. It separates the handling of Logite from the generic lgff driver
    and adds additional features specific for the Logitech wheels, namely

    - Native mode support for Driving Force GT, Driving Force Pro, G25 and G27
    wheels Every Logitech wheel reports itself as generic Logitech Driving Force
    wheel (VID 046d, PID c294). This is done to ensu wheel will work on every USB
    HID-aware system even when no Logitech driver is available. It however limits
    the capabilit wheel - range is limited to 200 degrees, G25/G27 don't report the
    clutch pedal and there is only one combined axis for t brake. The switch to
    native mode is done via hardware-specific command which is different for each
    wheel. When the wheel receives such command, it simulates reconnect and reports
    to the OS with its actual PID.

    - Adjustable wheel range DFGT, DFP, G25 and G27 have variable range of the
    steering wheel. The range is limited by applying a maximum constant when the
    wheel is turned beyond the allowed range. The limit as also set by a
    hardware-specific command. There is a comm command for DFGT, G25 and G27 and
    another one for DFP. It is probably possible to use the DFP command to limit
    the range other Logitech wheels too, but this is not supported by the official
    Logitech driver for Windows. The patch adds a sysfs interface which allows for
    the range to be set from userspace.

    - Fixed autocentering command All Logitech wheels support FF_AUTOCENTER effect.
    The original implementation in the lgff driver didn't work well with patch
    fixes it. According to USB communication sniffs the Formula Force EX (pretty
    much rebranded original Driving Force accept the generic autocentering command,
    this issue is also addressed by the patch

    There are still some features this patch doesn't cover, but since some of them
    will most likely require modifications of memless driver we have decided not to
    include them yet.

    As first we decided to move the handling of Logitech wheels from hid-lgff
    driver to hid-lg4ff driver (originally used fo At also adds PID of Logitech
    Driving Force GT.

    Signed-off-by: Michal Malý
    Signed-off-by: Simon Wood
    Signed-off-by: Jiri Kosina

    Michal Malý
     

02 Aug, 2011

1 commit

23 Jul, 2011

1 commit

21 Jul, 2011

1 commit

12 Jul, 2011

1 commit

11 Jul, 2011

2 commits

27 Jun, 2011

1 commit

  • d946e65e2   HID: add FF support for Holtek On Line Grip based gamepads ... Browse Code »

    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
     

24 Jun, 2011

1 commit

14 Jun, 2011

1 commit

08 Jun, 2011

1 commit

  • 74bc69531   HID: Add driver to fix Speedlink VAD Cezanne support ... Browse Code »

    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