summaryrefslogtreecommitdiffstats
path: root/samples/uhid
diff options
context:
space:
mode:
authorJiri Kosina <jkosina@suse.cz>2013-08-09 11:34:19 +0200
committerJiri Kosina <jkosina@suse.cz>2013-08-09 11:34:19 +0200
commit8e5654ce6914b950b42d1f896f3d8a75fbf307ae (patch)
treef03473054ad2582e5322571eb84c00703362df63 /samples/uhid
parentf9ed432c929f005110c23eb00702265fc4c08e66 (diff)
downloadlinux-8e5654ce6914b950b42d1f896f3d8a75fbf307ae.tar.gz
linux-8e5654ce6914b950b42d1f896f3d8a75fbf307ae.tar.bz2
linux-8e5654ce6914b950b42d1f896f3d8a75fbf307ae.zip
Revert "HID: hid-logitech-dj: querying_devices was never set"
This reverts commit 407a2c2a4d85100c8c67953e4bac2f4a6c942335. Explanation provided by Benjamin Tissoires: Commit "HID: hid-logitech-dj, querying_devices was never set" activate a flag which guarantees that we do not ask the receiver for too many enumeration. When the flag is set, each following enumeration call is discarded (the usb request is not forwarded to the receiver). The flag is then released when the driver receive a pairing information event, which normally follows the enumeration request. However, the USB3 bug makes the driver think the enumeration request has been forwarded to the receiver. However, it is actually not the case because the USB stack returns -EPIPE. So, when a new unknown device appears, the workaround consisting in asking for a new enumeration is not working anymore: this new enumeration is discarded because of the flag, which is never reset. A solution could be to trigger a timeout before releasing it, but for now, let's just revert the patch. Reported-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Tested-by: Sune Mølgaard <sune@molgaard.org> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'samples/uhid')
0 files changed, 0 insertions, 0 deletions