public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: feng <alec.jiang@gmail.com>
To: dtor@mail.ru
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	feng <alec.jiang@gmail.com>
Subject: [PATCH] Input: i8042 - add quirk for ASUS Zenbook UX425QA_UM425QA
Date: Wed, 21 Jan 2026 20:39:57 -0500	[thread overview]
Message-ID: <20260122013957.11184-1-alec.jiang@gmail.com> (raw)

The ASUS Zenbook UX425QA_UM425QA fails to initialize the keyboard after a
cold boot.

A quirk already exists for "ZenBook UX425", but some Zenbooks report "Zenbook" with a lowercase 'b'.
Since DMI matching is case-sensitive, the existing quirk is not applied to these "extra special" Zenbooks.

Testing confirms that this model needs the same quirks as the ZenBook UX425 variants.

Signed-off-by: feng <alec.jiang@gmail.com>
---
 drivers/input/serio/i8042-acpipnpio.h | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/drivers/input/serio/i8042-acpipnpio.h b/drivers/input/serio/i8042-acpipnpio.h
index 654771275..b34d922a9 100644
--- a/drivers/input/serio/i8042-acpipnpio.h
+++ b/drivers/input/serio/i8042-acpipnpio.h
@@ -115,6 +115,16 @@ static const struct dmi_system_id i8042_dmi_quirk_table[] __initconst = {
 		},
 		.driver_data = (void *)(SERIO_QUIRK_NOMUX | SERIO_QUIRK_RESET_NEVER)
 	},
+	/* ASUS Zenbook UX425QA_UM425QA
+	 * Some Zenbooks report "Zenbook" with a lowercase b.
+	 */
+	{
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
+			DMI_MATCH(DMI_PRODUCT_NAME, "Zenbook UX425QA_UM425QA"),
+		},
+		.driver_data = (void *)(SERIO_QUIRK_PROBE_DEFER | SERIO_QUIRK_RESET_NEVER)
+	},
 	{
 		/* ASUS ZenBook UX425UA/QA */
 		.matches = {
-- 
2.34.1


             reply	other threads:[~2026-01-22  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22  1:39 feng [this message]
2026-01-25  5:47 ` [PATCH] Input: i8042 - add quirk for ASUS Zenbook UX425QA_UM425QA Dmitry Torokhov
2026-01-25  5:51 ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260122013957.11184-1-alec.jiang@gmail.com \
    --to=alec.jiang@gmail.com \
    --cc=dtor@mail.ru \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox