Commit aaa4ca87 authored by Werner Sembach's avatar Werner Sembach Committed by Dmitry Torokhov

Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination

The old quirk combination sometimes cause a laggy keyboard after boot. With
the new quirk the initial issue of an unresponsive keyboard after s3 resume
is also fixed, but it doesn't have the negative side effect of the
sometimes laggy keyboard.
Signed-off-by: default avatarWerner Sembach <wse@tuxedocomputers.com>
Cc: stable@vger.kernel.org
Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
Link: https://lore.kernel.org/r/20240104183118.779778-3-wse@tuxedocomputers.comSigned-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
parent 3d765ae2
...@@ -1159,18 +1159,10 @@ static const struct dmi_system_id i8042_dmi_quirk_table[] __initconst = { ...@@ -1159,18 +1159,10 @@ static const struct dmi_system_id i8042_dmi_quirk_table[] __initconst = {
SERIO_QUIRK_NOLOOP | SERIO_QUIRK_NOPNP) SERIO_QUIRK_NOLOOP | SERIO_QUIRK_NOPNP)
}, },
{ {
/*
* Setting SERIO_QUIRK_NOMUX or SERIO_QUIRK_RESET_ALWAYS makes
* the keyboard very laggy for ~5 seconds after boot and
* sometimes also after resume.
* However both are required for the keyboard to not fail
* completely sometimes after boot or resume.
*/
.matches = { .matches = {
DMI_MATCH(DMI_BOARD_NAME, "N150CU"), DMI_MATCH(DMI_BOARD_NAME, "N150CU"),
}, },
.driver_data = (void *)(SERIO_QUIRK_NOMUX | SERIO_QUIRK_RESET_ALWAYS | .driver_data = (void *)(SERIO_QUIRK_FORCENORESTORE)
SERIO_QUIRK_NOLOOP | SERIO_QUIRK_NOPNP)
}, },
{ {
.matches = { .matches = {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment