summaryrefslogtreecommitdiffstats
path: root/fs/fscache
diff options
context:
space:
mode:
authorJim Keir <jimkeir@oracledbadirect.com>2015-02-26 10:14:03 +0100
committerJiri Kosina <jkosina@suse.cz>2015-03-16 16:11:48 +0100
commite8f46e4f93f52b2bcc681cf8bc3ff84a22a2d356 (patch)
tree601883a2ea06ce94880bf2803851609fdcf61d07 /fs/fscache
parentHID: samples/hidraw: make it possible to select device (diff)
downloadlinux-e8f46e4f93f52b2bcc681cf8bc3ff84a22a2d356.tar.xz
linux-e8f46e4f93f52b2bcc681cf8bc3ff84a22a2d356.zip
HID: pidff: support more than one concurrent effect
The PID driver (usbhid/hid-pidff.c) does not set the effect ID when uploading an effect. The result is that the initial upload works but subsequent uploads to modify effect parameters are all directed at the last-created effect. The targeted effect ID must be passed back to the device when effect parameters are changed. This is done at the start of "pidff_set_condition_report", "pidff_set_periodic_report" etc. based on the value of "pidff->block_load[PID_EFFECT_ BLOCK_INDEX].value[0]". This value is only ever set during pidff_request_effect_upload. The result is stored in "pidff->pid_id[effect->id]" at the end of pid_upload_effect, for later use. However, if an effect is modified and re-sent then this identifier is not being copied back from pidff->pid_id[effect->id] before sending the command to the device. The fix is to do this at the start of pidff_upload_effect. Signed-off-by: Jim Keir <jimkeir@oracledbadirect.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'fs/fscache')
0 files changed, 0 insertions, 0 deletions