From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Werner Sembach <wse@tuxedocomputers.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Christoffer Sandberg <cs@tuxedo.de>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ACPI: resource: Do IRQ override on TongFang GXxHRXx and GMxHGxx
Date: Mon, 22 Apr 2024 18:28:13 +0200 [thread overview]
Message-ID: <CAJZ5v0iLjEsjzOU+0it9=NVoqzsrErz1Fs_eVQg-sJgXVqf8jQ@mail.gmail.com> (raw)
In-Reply-To: <20240422080437.912886-1-wse@tuxedocomputers.com>
On Mon, Apr 22, 2024 at 10:04 AM Werner Sembach <wse@tuxedocomputers.com> wrote:
>
> From: Christoffer Sandberg <cs@tuxedo.de>
>
> Listed devices need the override for the keyboard to work.
>
> Signed-off-by: Christoffer Sandberg <cs@tuxedo.de>
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/acpi/resource.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
> index 59423fe9d0f29..6cc8572759a3d 100644
> --- a/drivers/acpi/resource.c
> +++ b/drivers/acpi/resource.c
> @@ -630,6 +630,18 @@ static const struct dmi_system_id irq1_edge_low_force_override[] = {
> DMI_MATCH(DMI_BOARD_NAME, "X565"),
> },
> },
> + {
> + /* TongFang GXxHRXx/TUXEDO InfinityBook Pro Gen9 AMD */
> + .matches = {
> + DMI_MATCH(DMI_BOARD_NAME, "GXxHRXx"),
> + },
> + },
> + {
> + /* TongFang GMxHGxx/TUXEDO Stellaris Slim Gen1 AMD */
> + .matches = {
> + DMI_MATCH(DMI_BOARD_NAME, "GMxHGxx"),
> + },
> + },
> { }
> };
>
> --
Applied as 6.10 material, thanks!
prev parent reply other threads:[~2024-04-22 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 8:04 [PATCH v2] ACPI: resource: Do IRQ override on TongFang GXxHRXx and GMxHGxx Werner Sembach
2024-04-22 16:28 ` 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='CAJZ5v0iLjEsjzOU+0it9=NVoqzsrErz1Fs_eVQg-sJgXVqf8jQ@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=cs@tuxedo.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wse@tuxedocomputers.com \
/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).