| commit | c2b2f16c5c62583d4f8904e44c4b30c94a01eaf1 | |
| author | David Herrmann <dh.herrmann@gmail.com> | |
| Tue, 29 Jul 2014 15:14:25 +0000 (29 17:14 +0200) | ||
| committer | Jiri Kosina <jkosina@suse.cz> | |
| Mon, 25 Aug 2014 08:28:08 +0000 (25 03:28 -0500) | ||
| tree | 72ff984b458a6ff721a67a062fc11fe6c9548a26 | treesnapshot (tar.gz zip) |
| parent | 11c221553080408b203a00b91ad5f647dfb218d1 | commitdiff |
HID: uhid: report to user-space whether reports are numbered
This makes UHID_START include a "dev_flags" field that describes details
of the hid-device in the kernel. The first flags we introduce describe
whether a given report-type uses numbered reports. This is useful for
transport layers that force report-numbers and therefore might have to
prefix kernel-provided HID-messages with the report-number.
Currently, only HoG needs this and the spec only talks about "global
report numbers". That is, it's a global boolean not a per-type boolean.
However, given the quirks we already have in kernel-space, a per-type
value seems much more appropriate.
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This makes UHID_START include a "dev_flags" field that describes details
of the hid-device in the kernel. The first flags we introduce describe
whether a given report-type uses numbered reports. This is useful for
transport layers that force report-numbers and therefore might have to
prefix kernel-provided HID-messages with the report-number.
Currently, only HoG needs this and the spec only talks about "global
report numbers". That is, it's a global boolean not a per-type boolean.
However, given the quirks we already have in kernel-space, a per-type
value seems much more appropriate.
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
| drivers/hid/uhid.c | diffblobblamehistory | |
| include/uapi/linux/uhid.h | diffblobblamehistory |