diff options
| author | Igor Mammedov <imammedo@redhat.com> | 2011-04-18 21:17:17 +0400 |
|---|---|---|
| committer | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2011-04-18 21:17:45 +0400 |
| commit | c36b58e8a9112017c2bcc322cc98e71241814303 (patch) | |
| tree | 64a4a1b7d7719ef40451493a2c049b3b1ddfd5bb /drivers/input/touchscreen/wm831x-ts.c | |
| parent | 80b4895aa4578e9372d76cd4063f82d0c3994d77 (diff) | |
| download | linux-c36b58e8a9112017c2bcc322cc98e71241814303.tar.xz | |
Input: xen-kbdfront - fix mouse getting stuck after save/restore
Mouse gets "stuck" after restore of PV guest but buttons are in working
condition.
If driver has been configured for ABS coordinates at start it will get
XENKBD_TYPE_POS events and then suddenly after restore it'll start getting
XENKBD_TYPE_MOTION events, that will be dropped later and they won't get
into user-space.
Regression was introduced by hunk 5 and 6 of
5ea5254aa0ad269cfbd2875c973ef25ab5b5e9db
("Input: xen-kbdfront - advertise either absolute or relative
coordinates").
Driver on restore should ask xen for request-abs-pointer again if it is
available. So restore parts that did it before 5ea5254.
Acked-by: Olaf Hering <olaf@aepfle.de>
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
[v1: Expanded the commit description]
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Diffstat (limited to 'drivers/input/touchscreen/wm831x-ts.c')
0 files changed, 0 insertions, 0 deletions