diff options
| author | Oleksij Rempel <linux@rempel-privat.de> | 2016-09-12 17:48:17 +0200 |
|---|---|---|
| committer | Darren Hart <dvhart@linux.intel.com> | 2016-09-23 17:06:20 -0700 |
| commit | b5643539b82559b858b8efe3fc8343f66cf9a0b5 (patch) | |
| tree | 75ab060185392155db9458d856a7ac158bac21e6 /include | |
| parent | 28e476d7438eedd3ecc7b5ebe6f2a3dfd21ca10e (diff) | |
platform/x86: asus-wmi: Filter buggy scan codes on ASUS Q500A
Some revisions of the ASUS Q500A series have a keyboard related
issue which is reproducible only after Windows with installed ASUS
tools is started.
In this case the Linux side will have a blocked keyboard or
report incorrect or incomplete hotkey events.
To make Linux work properly again, a complete power down
(unplug power supply and remove battery) is needed.
Linux/atkbd after a clean start will get the following code on VOLUME_UP
key: {0xe0, 0x30, 0xe0, 0xb0}. After Windows, the same key will generate
this codes: {0xe1, 0x23, 0xe0, 0x30, 0xe0, 0xb0}. As result atkdb will
be confused by buggy codes.
This patch is filtering this buggy code out.
https://bugzilla.kernel.org/show_bug.cgi?id=119391
Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
Cc: Alex Henrie <alexhenrie24@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Corentin Chary <corentin.chary@gmail.com>
Cc: acpi4asus-user@lists.sourceforge.net
Cc: platform-driver-x86@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
[dvhart: Add return after pr_warn to avoid false confirmation of filter]
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions