aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/hid/hid-elecom.c
diff options
context:
space:
mode:
authorBenjamin Tissoires <benjamin.tissoires@redhat.com>2019-04-20 13:22:05 +0200
committerBenjamin Tissoires <benjamin.tissoires@redhat.com>2019-04-23 18:02:39 +0200
commit91cf9a98ae4127551d022e287e283bcd8738ed02 (patch)
tree6bc3be96ebb24388d2690e259924fd5f8a7ba0f3 /drivers/hid/hid-elecom.c
parentHID: logitech-hidpp: allow non HID++ devices to be handled by this module (diff)
downloadlinux-dev-91cf9a98ae4127551d022e287e283bcd8738ed02.tar.xz
linux-dev-91cf9a98ae4127551d022e287e283bcd8738ed02.zip
HID: logitech-hidpp: make .probe usbhid capable
The current custom solution for the G920 is not the best because hid_hw_start() is not called at the end of the .probe(). It means that any configuration retrieved after the initial hid_hw_start would not be exposed to user space without races. We can simply force hid_hw_start to just enable the transport layer by not using a connect_mask. This way, we can have a common path between USB, Unifying and Bluetooth devices. With this change, we can now support the non DJ receivers for low end devices, which will allow us to fetch the actual names of the paired device (instead of 'Logitech Wireless Receiver') Tested with a M185 with the non unifying receiver, a T650 and many other unifying devices, and the T651 over Bluetooth. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Diffstat (limited to 'drivers/hid/hid-elecom.c')
0 files changed, 0 insertions, 0 deletions