linux.git/drivers/hid/hid-input.c, branch v3.4

Merge branches 'battery-scope', 'logitech' and 'multitouch' into for-linus

2012-03-20T12:04:25+00:00

HID: hid-input: allow array fields out of range

2012-03-05T09:28:58+00:00

Allow array field values out of range as per HID 1.11 specification,
section 6.2.25:

	Rather than returning a single bit for each button in the group, an
	array returns an index in each field that corresponds to the pressed
	button (like keyboard scan codes). An out-of range value in and array
	field is considered no controls asserted.

Apparently, "and" above is a typo and should be "an".

This fixes at least Waltop tablet pen clicks - otherwise BTN_TOUCH is never
released.

The relevant part of Waltop tablet report descriptors is this:

	0x09, 0x42,         /*          Usage (Tip Switch),         */
	0x09, 0x44,         /*          Usage (Barrel Switch),      */
	0x09, 0x46,         /*          Usage (Tablet Pick),        */
	0x15, 0x01,         /*          Logical Minimum (1),        */
	0x25, 0x03,         /*          Logical Maximum (3),        */
	0x75, 0x04,         /*          Report Size (4),            */
	0x95, 0x01,         /*          Report Count (1),           */
	0x80,               /*          Input,                      */

This is a regression fix for commit b4b583d ("HID: be more strict when
ignoring out-of-range fields").

Signed-off-by: Nikolai Kondrashov 
Signed-off-by: Jiri Kosina

HID: hid-input/battery: set scope and powered device for HID battery

2012-02-03T22:54:58+00:00

Set the battery's power supply scope to "Device" and point the power
supply to the powered device.

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

Merge branch 'hid-battery' of git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen into for-linus

2012-01-09T10:24:59+00:00

hid-input/battery: add FEATURE quirk

2012-01-08T07:31:25+00:00

Apple keyboards require a FEATURE report to query the battery state,
even though they list as an input.  Without this, it returns an error.

Signed-off-by: Jeremy Fitzhardinge

hid-input/battery: remove battery_val

2012-01-08T07:31:18+00:00

hidinput_get_battery_property() now directly polls the device for the
current battery strength, so there's no need for battery_val, or the
code to set it on the input event path.

Signed-off-by: Jeremy Fitzhardinge

hid-input/battery: power-supply type really is a battery

2012-01-08T07:30:39+00:00

It just isn't a battery which is powering the computer.  upower needs
a more nuanced understanding of this.

Signed-off-by: Jeremy Fitzhardinge

hid-input/battery: make the battery setup common for INPUTs and FEATUREs

2012-01-08T07:30:38+00:00

Signed-off-by: Jeremy Fitzhardinge

hid-input/battery: deal with both FEATURE and INPUT report batteries

2012-01-08T07:30:37+00:00

Some devices seem to report batteries as FEATUREs, others as INPUTs.

Signed-off-by: Jeremy Fitzhardinge

hid-input/battery: add quirks for battery