diff options
author | 2014-09-30 13:18:30 -0400 | |
---|---|---|
committer | 2014-10-29 10:51:40 +0100 | |
commit | 33797820af98cde5c7cee00d00f0d8e255ea199f (patch) | |
tree | 2d85919e568b520986c52fed4af86d077f755bf9 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | HID: logitech-dj: allow transfer of HID++ reports from/to the correct dj device (diff) | |
download | linux-dev-33797820af98cde5c7cee00d00f0d8e255ea199f.tar.xz linux-dev-33797820af98cde5c7cee00d00f0d8e255ea199f.zip |
HID: logitech: allow the DJ device to request the unifying name
The names of the DJ devices are stored in the receiver. These names
can be retrieved through a HID++ command. However, the protocol says
that you have to ask the receiver for that, not the device iteself.
Introduce a special case in the DJ handling where a device can request
its unifying name, and when such a name is given, forward it also to
the corresponding device.
On the HID++ side, the receiver talks only HID++ 1.0, so we need to
implement this part of the protocol in the module.
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Tested-by: Andrew de los Reyes <adlr@chromium.org>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions