diff options
| author | Lyude <lyude@redhat.com> | 2017-07-22 21:15:09 -0400 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2017-09-08 15:00:52 +0200 |
| commit | cac72b990d34f4c70208998a86f910ba38253c94 (patch) | |
| tree | 2c358932e4a0e67fc584cb1fa805d89a80852046 /lib/syscall.c | |
| parent | fcaa4a07d2a4b541e91da7a55d8b3331f96d1865 (diff) | |
HID: rmi: Make sure the HID device is opened on resume
So it looks like that suspend/resume has actually always been broken on
hid-rmi. The fact it worked was a rather silly coincidence that was
relying on the HID device to already be opened upon resume. This means
that so long as anything was reading the /dev/input/eventX node for for
an RMI device, it would suspend and resume correctly. As well, if
nothing happened to be keeping the HID device away it would shut off,
then the RMI driver would get confused on resume when it stopped
responding and explode.
So, call hid_hw_open() in rmi_post_resume() so we make sure that the
device is alive before we try talking to it.
This fixes RMI device suspend/resume over HID.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=196851
[jkosina@suse.cz: removed useless hunk that was zero-initializing 'ret']
Signed-off-by: Lyude <lyude@redhat.com>
Cc: Andrew Duggan <aduggan@synaptics.com>
Cc: stable@vger.kernel.org
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'lib/syscall.c')
0 files changed, 0 insertions, 0 deletions