linux-toradex.git/drivers/hid/hid-kye.c, branch v4.1.14

HID: kye: Fix report descriptor for Genius PenSketch M912

2015-02-17T12:13:45+00:00

Genius PenSketch M912 digitizer tablet sends incorrect report descriptor by
default. This patch replaces it with a corrected one.

Signed-off-by: Milan Plzik 
Reviewed-by: Nikolai Kondrashov 
Signed-off-by: Jiri Kosina

HID: Add a new id 0x501a for Genius MousePen i608X

2014-12-29T10:12:37+00:00

New Genius MousePen i608X devices have a new id 0x501a instead of the
old 0x5011 so add a new #define with "_2" appended and change required
places.

The remaining two checkpatch warnings about line length
being over 80 characters are present in the original files too and this
patch was made in the same style (no line break).

Just adding a new id and changing the required places should make the
new device work without any issues according to the bug report in the
following url.

This patch was made according to and fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=67111

Signed-off-by: Giedrius Statkevičius 
Signed-off-by: Jiri Kosina

HID: fix a couple of off-by-ones

2014-08-21T15:43:28+00:00

There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.

Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes 
Reviewed-by: Benjamin Tissoires 
Signed-off-by: Jiri Kosina

HID: kye: Fix missing break in kye_report_fixup()

2013-12-02T14:17:04+00:00

The change to support Genius Manticore Keyboard also changed behaviour
for Genius Gx Imperator Keyboard, as there is no break between the
cases.  This is presumably a mistake.

Reported by Coverity as CID 1134029.

Fixes: 4a2c94c9b6c0 ('HID: kye: Add report fixup for Genius Manticore Keyboard')
Signed-off-by: Ben Hutchings 
Signed-off-by: Jiri Kosina

HID: kye: fix unresponsive keyboard

2013-11-21T09:28:58+00:00

The manticore keyboard requires that all usb EP are opened at least
once to be fully functional. The third EP forwards to the user space
some vendor specific information about the keyboard state, but are useless
currently for the kernel.

Opening them and closing them makes the keyboard responsive again.

Reported-and-tested-by: Adam Kulagowski 
Signed-off-by: Benjamin Tissoires 
Signed-off-by: Jiri Kosina

HID: kye: Add report fixup for Genius Manticore Keyboard

2013-11-21T09:28:58+00:00

Genius Manticore Keyboard presents the same problem in its report
descriptors than Genius Gila Gaming Mouse and Genius Imperator Keyboard.
Use the same fixup.

Reported-and-tested-by: Adam Kulagowski 
Signed-off-by: Benjamin Tissoires 
Signed-off-by: Jiri Kosina

HID: kye: Add report fixup for Genius Gx Imperator Keyboard

2013-07-15T08:25:33+00:00

Genius Gx Imperator Keyboard presents the same problem in its report
descriptors than Genius Gila Gaming Mouse.
Use the same fixup for both.

Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=928561

Reported-and-tested-by: Honza Brazdil 
Signed-off-by: Benjamin Tissoires 
Signed-off-by: Jiri Kosina

HID: kye: Add report fixup for Genius Gila Gaming mouse

2013-07-03T16:14:33+00:00

Genius Gila Gaming Mouse presents an obviously wrong report descriptor.
the Consumer control (report ID 3) is the following:
0x05, 0x0c,                    // Usage Page (Consumer Devices)       105
0x09, 0x01,                    // Usage (Consumer Control)            107
0xa1, 0x01,                    // Collection (Application)            109
0x85, 0x03,                    //   Report ID (3)                     111
0x19, 0x00,                    //   Usage Minimum (0)                 113
0x2a, 0xff, 0x7f,              //   Usage Maximum (32767)             115
0x15, 0x00,                    //   Logical Minimum (0)               118
0x26, 0xff, 0x7f,              //   Logical Maximum (32767)           120
0x75, 0x10,                    //   Report Size (16)                  123
0x95, 0x03,                    //   Report Count (3)                  125
0x81, 0x00,                    //   Input (Data,Arr,Abs)              127
0x75, 0x08,                    //   Report Size (8)                   129
0x95, 0x01,                    //   Report Count (1)                  131
0x81, 0x01,                    //   Input (Cnst,Arr,Abs)              133
0xc0,                          // End Collection                      135

So the first input whithin this report has a count of 3 but a usage range
of 32768. So this value is obviously wrong as it should not be greater than
the report count.

Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=959721

Signed-off-by: Benjamin Tissoires 
Signed-off-by: Jiri Kosina

HID: use hid_hw_request() instead of direct call to usbhid

2013-02-25T12:26:41+00:00

This allows the hid drivers to be independent from the transport layer.

The patch was constructed by replacing all occurences of
usbhid_submit_report() by its hid_hw_request() counterpart.
Then, drivers not requiring USB_HID anymore have their USB_HID
dependency cleaned in the Kconfig file.

Finally, few drivers still depends on USB_HID. Many of them
are requiring the io wait callback. They are found in the next patch.

Signed-off-by: Benjamin Tissoires 
Reviewed-by: Mika Westerberg 

For the sensor-hub part:
Tested-by: Mika Westerberg 
Signed-off-by: Jiri Kosina

HID: Use module_hid_driver macro

2013-01-03T09:27:31+00:00

Use the new module_hid_driver macro in all HID drivers that have
a simple register/unregister init/exit.

This also converts the hid drivers that test for a failure of
hid_register_driver() and report the failure. Using module_hid_driver
in those drivers removes the failure message.

Signed-off-by: H Hartley Sweeten 
Signed-off-by: Jiri Kosina