aboutsummaryrefslogtreecommitdiffstats
path: root/samples
diff options
context:
space:
mode:
authorDavid Herrmann <dh.herrmann@googlemail.com>2012-06-10 15:16:25 +0200
committerHumberto Borba <humberos@gmail.com>2013-01-12 21:05:36 -0200
commitc9410c292f41530652d2945c74651b67933bc34f (patch)
tree08322b67fb60afb1ab90bb0a01c6ee71495d86ec /samples
parentff7beda4147cb452943acb3d26ed513b013ad852 (diff)
downloadkernel_samsung_smdk4412-c9410c292f41530652d2945c74651b67933bc34f.zip
kernel_samsung_smdk4412-c9410c292f41530652d2945c74651b67933bc34f.tar.gz
kernel_samsung_smdk4412-c9410c292f41530652d2945c74651b67933bc34f.tar.bz2
HID: uhid: implement feature requests
HID standard allows sending a feature request to the device which is answered by an HID report. uhid implements this by sending a UHID_FEATURE event to user-space which then must answer with UHID_FEATURE_ANSWER. If it doesn't do this in a timely manner, the request is discarded silently. We serialize the feature requests, that is, there is always only a single active feature-request sent to user-space, other requests have to wait. HIDP and USB-HID do it the same way. Because we discard feature-requests silently, we must make sure to match a response to the corresponding request. We use sequence-IDs for this so user-space must copy the ID from the request into the answer. Feature-answers are ignored if they do not contain the same ID as the currently pending feature request. Internally, we must make sure that feature-requests are synchronized with UHID_DESTROY and close() events. We must not dead-lock when closing the HID device, either, so we have to use separate locks. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions