From: Werner Sembach <wse@tuxedocomputers.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Len Brown <lenb@kernel.org>
Cc: Christoffer Sandberg <cs@tuxedo.de>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: resource: Do IRQ override on TongFang GXxHRXx and GMxHGxx
Date: Wed, 17 Apr 2024 17:55:32 +0200 [thread overview]
Message-ID: <d5d5e679-8456-4f78-9569-ffb7f7240373@tuxedocomputers.com> (raw)
In-Reply-To: <20240417103509.28657-1-wse@tuxedocomputers.com>
Sorry noticed and issue with this, please don't apply, I will send a v2.
Am 17.04.24 um 12:35 schrieb Werner Sembach:
> From: Christoffer Sandberg <cs@tuxedo.de>
>
> Listed devices needs the override for 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..deeb4e182687a 100644
> --- a/drivers/acpi/resource.c
> +++ b/drivers/acpi/resource.c
> @@ -558,6 +558,18 @@ static const struct dmi_system_id irq1_edge_low_force_override[] = {
> DMI_MATCH(DMI_BOARD_NAME, "GM6XGxX"),
> },
> },
> + {
> + .ident = "TongFang GXxHRXx/TUXEDO InfinityBook Pro Gen9 AMD",
> + .matches = {
> + DMI_MATCH(DMI_PRODUCT_SKU, "GXxHRXx"),
> + },
> + },
> + {
> + .ident = "TongFang GMxHGxx/TUXEDO Stellaris Slim Gen1 AMD",
> + .matches = {
> + DMI_MATCH(DMI_PRODUCT_SKU, "GMxHGxx"),
> + },
> + },
> {
> /* MAINGEAR Vector Pro 2 15 */
> .matches = {
prev parent reply other threads:[~2024-04-17 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 10:35 [PATCH] ACPI: resource: Do IRQ override on TongFang GXxHRXx and GMxHGxx Werner Sembach
2024-04-17 15:55 ` Werner Sembach [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=d5d5e679-8456-4f78-9569-ffb7f7240373@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=cs@tuxedo.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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).