Re: [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

2018-05-29 Thread Jiri Kosina
On Fri, 25 May 2018, Benjamin Tissoires wrote: > When we receive a RMI4 report, we should not unconditionally send an > input_sync event. Instead, we should let the rmi4 transport layer do it > for us. > > This fixes a situation where we might receive X in a report and the rest > in a subsequent

Re: [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

2018-05-28 Thread Benjamin Tissoires
On Fri, May 25, 2018 at 2:51 PM, Benjamin Tissoires wrote: > When we receive a RMI4 report, we should not unconditionally send an > input_sync event. Instead, we should let the rmi4 transport layer do it > for us. > > This fixes a situation where we might receive X in a report and the rest > in a

Re: [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

2018-05-27 Thread Peter Hutterer
On Fri, May 25, 2018 at 02:51:06PM +0200, Benjamin Tissoires wrote: > When we receive a RMI4 report, we should not unconditionally send an > input_sync event. Instead, we should let the rmi4 transport layer do it > for us. > > This fixes a situation where we might receive X in a report and the res

[PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

2018-05-25 Thread Benjamin Tissoires
When we receive a RMI4 report, we should not unconditionally send an input_sync event. Instead, we should let the rmi4 transport layer do it for us. This fixes a situation where we might receive X in a report and the rest in a subsequent one. And this messes up user space. Link: https://bugs.free