[PATCH] Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK)

[PATCH] Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK)

[Zeyu WANG]

The Lenovo Yoga Air 14 (83QK) laptop keyboard becomes unresponsive
after the standard atkbd init sequence. Controlled testing on the
actual hardware shows the F5 (ATKBD_CMD_RESET_DIS / deactivate)
command specifically corrupts the EC state, causing zero IRQ1
interrupts after init.

Skipping only the deactivate command (while keeping F4 ENABLE)
resolves the issue completely: both keystroke input and CapsLock
LED toggle work correctly. The reverse test - skipping only F4
while keeping F5 - makes the problem worse (zero keystroke
interrupts), confirming F5 is the sole culprit.

Add a DMI quirk entry for LENOVO/83QK using the existing
atkbd_deactivate_fixup callback, consistent with the existing
entries for LG Electronics and HONOR FMB-P that address the
same EC F5 deactivate issue.

Signed-off-by: Zeyu WANG <zeyu.thomas.wang@gmail.com>
---
 drivers/input/keyboard/atkbd.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
index c8ad55f..217e66e 100644
--- a/drivers/input/keyboard/atkbd.c
+++ b/drivers/input/keyboard/atkbd.c
@@ -1923,6 +1923,14 @@ static const struct dmi_system_id atkbd_dmi_quirk_table[] __initconst = {
 		},
 		.callback = atkbd_deactivate_fixup,
 	},
+	{
+		/* Lenovo Yoga Air 14 (83QK) */
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "83QK"),
+		},
+		.callback = atkbd_deactivate_fixup,
+	},
 	{ }
 };
 
-- 
2.53.0

Re: [PATCH] Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK)

[Dmitry Torokhov]

On Wed, Jun 03, 2026 at 01:09:09AM +0800, Zeyu WANG wrote:
> The Lenovo Yoga Air 14 (83QK) laptop keyboard becomes unresponsive
> after the standard atkbd init sequence. Controlled testing on the
> actual hardware shows the F5 (ATKBD_CMD_RESET_DIS / deactivate)
> command specifically corrupts the EC state, causing zero IRQ1
> interrupts after init.
> 
> Skipping only the deactivate command (while keeping F4 ENABLE)
> resolves the issue completely: both keystroke input and CapsLock
> LED toggle work correctly. The reverse test - skipping only F4
> while keeping F5 - makes the problem worse (zero keystroke
> interrupts), confirming F5 is the sole culprit.
> 
> Add a DMI quirk entry for LENOVO/83QK using the existing
> atkbd_deactivate_fixup callback, consistent with the existing
> entries for LG Electronics and HONOR FMB-P that address the
> same EC F5 deactivate issue.
> 
> Signed-off-by: Zeyu WANG <zeyu.thomas.wang@gmail.com>

Applied, thank you.

-- 
Dmitry