diff options
| author |   Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2016-12-09 12:57:39 -0800 |
|---|---|---|
| committer |   Thomas Gleixner <tglx@linutronix.de> | 2016-12-19 11:34:15 +0100 |
| commit | d79e141c1c6ea7cb70c169971d522b88c8d5b419 (patch) | |
| tree | 49cdd9f0992b882dd0542311f04475f669168764 /arch | |
| parent | x86/init: Add i8042 state to the platform data (diff) | |
| download | linux-dev-d79e141c1c6ea7cb70c169971d522b88c8d5b419.tar.xz linux-dev-d79e141c1c6ea7cb70c169971d522b88c8d5b419.zip | |
Input: i8042 - Trust firmware a bit more when probing on X86
The error message "Can't read CTR while initializing i8042" appears on
Cherry Trail-based devices at each boot time:
i8042: PNP: No PS/2 controller found. Probing ports directly.
i8042: Can't read CTR while initializing i8042
i8042: probe of i8042 failed with error -5
This happens because we historically do not trust firmware on X86 and,
while noting that PNP does not show keyboard or mouse devices, we still
charge ahead and try to probe the controller. Let's relax this a bit and if
results of PNP probe agree with the results of platform
initialization/quirks conclude that there is, in fact, no i8042.
While at it, let's avoid using x86_platform.i8042_detect() and instead
abort execution early if platform indicates that it can not possibly have
i8042 (x86_platform.legacy.i8042 equals X86_LEGACY_I8042_PLATFORM_ABSENT).
Reported-and-tested-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Acked-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: linux-input@vger.kernel.org
Link: http://lkml.kernel.org/r/1481317061-31486-3-git-send-email-dmitry.torokhov@gmail.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions