From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Guenter Schafranek <gschafra@web.de>
Cc: rafael@kernel.org, lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: resource: Do IRQ override on GMxBGxx (XMG APEX 17 M23)
Date: Mon, 22 Apr 2024 18:23:51 +0200 [thread overview]
Message-ID: <CAJZ5v0jmtH6+C=GcWxXLM3qXBoMvuC-Nz8fuBG=1Ha1g95atGw@mail.gmail.com> (raw)
In-Reply-To: <20240415185120.57973-1-gschafra@web.de>
On Mon, Apr 15, 2024 at 8:51 PM Guenter Schafranek <gschafra@web.de> wrote:
>
> The XM APEX 17 M23 (TongFang?) GMxBGxx (got using `sudo dmidecode -s
> baseboard-product-name`) needs IRQ overriding for the keyboard to work.
> Adding an entry for this laptop to the override_table makes the internal
> keyboard functional.
> See https://www.reddit.com/r/XMG_gg/comments/15kd5pg/xmg_apex_17_m23_keyboard_not_working_on_linux/.
> Patch was successfully tested with Arch Linux Kernel v6.8 under
> Manjaro Linux v23.1.4.
>
> Signed-off-by: Guenter Schafranek <gschafra@web.de>
> ---
> drivers/acpi/resource.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
> index 59423fe9d..c9af5d2f4 100644
> --- a/drivers/acpi/resource.c
> +++ b/drivers/acpi/resource.c
> @@ -533,6 +533,12 @@ static const struct dmi_system_id irq1_level_low_skip_override[] = {
> * to have a working keyboard.
> */
> static const struct dmi_system_id irq1_edge_low_force_override[] = {
> + {
> + /* XMG APEX 17 (M23) */
> + .matches = {
> + DMI_MATCH(DMI_BOARD_NAME, "GMxBGxx"),
> + },
> + },
> {
> /* TongFang GMxRGxx/XMG CORE 15 (M22)/TUXEDO Stellaris 15 Gen4 AMD */
> .matches = {
> --
Applied as 6.10 material, thanks!
prev parent reply other threads:[~2024-04-22 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 18:51 [PATCH] ACPI: resource: Do IRQ override on GMxBGxx (XMG APEX 17 M23) Guenter Schafranek
2024-04-22 16:23 ` Rafael J. Wysocki [this message]
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='CAJZ5v0jmtH6+C=GcWxXLM3qXBoMvuC-Nz8fuBG=1Ha1g95atGw@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=gschafra@web.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).