summaryrefslogtreecommitdiffstats
path: root/drivers/input/keyboard/Kconfig
diff options
context:
space:
mode:
authorAndrew Duggan <aduggan@synaptics.com>2017-06-23 00:04:51 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2017-06-23 00:08:48 -0700
commit9768935264c4f0e4afd788a185d8e8d89c28e41d (patch)
tree35a8e2cc2b4e7e41e2afc7cce1cb2b7f365fe25d /drivers/input/keyboard/Kconfig
parent817ae460c784f32cd45e60b2b1b21378c3c6a847 (diff)
downloadlinux-stable-9768935264c4f0e4afd788a185d8e8d89c28e41d.tar.gz
linux-stable-9768935264c4f0e4afd788a185d8e8d89c28e41d.tar.bz2
linux-stable-9768935264c4f0e4afd788a185d8e8d89c28e41d.zip
Input: synaptics-rmi4 - only read the F54 query registers which are used
The F54 driver is currently only using the first 6 bytes of F54 so there is no need to read all 27 bytes. Some Dell systems (Dell XP13 9333 and similar) have an issue with the touchpad or I2C bus when reading reports larger then 16 bytes. Reads larger then 16 bytes are reported in two HID reports. Something about the back to back reports seems to cause the next read to report incorrect data. This results in F30 failing to load and the click button failing to work. Previous issues with the I2C controller or touchpad were addressed in: commit 5b65c2a02966 ("HID: rmi: check sanity of the incoming report") Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=195949 Signed-off-by: Andrew Duggan <aduggan@synaptics.com> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Reviewed-by: Nick Dyer <nick@shmanahar.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input/keyboard/Kconfig')
0 files changed, 0 insertions, 0 deletions