From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Tamim Khan <tamim@fusetak.com>
Cc: linux-acpi@vger.kernel.org, rafael@kernel.org, lenb@kernel.org,
Gianni <gianni.casagrande.mail@gmail.com>
Subject: Re: [PATCH] ACPI: resource: Skip IRQ override on Asus Vivobook Pro N6506MV
Date: Tue, 30 Apr 2024 21:23:40 +0200 [thread overview]
Message-ID: <CAJZ5v0jrw0frQPcMF94SWOSD=J4ktFyTo0jc1kuBKTsiHf-+Wg@mail.gmail.com> (raw)
In-Reply-To: <20240428170841.487584-1-tamim@fusetak.com>
On Sun, Apr 28, 2024 at 7:10 PM Tamim Khan <tamim@fusetak.com> wrote:
>
> Like various other Asus Vivobook and Expertbook laptops, the Asus
> Vivobook Pro N6506MV has a DSDT table that describes IRQ 1 as ActiveLow
> while the kernel is overriding it to Edge_High. This prevents the internal
> keyboard from working. This patch prevents this issue by adding this laptop
> to the override table that prevents the kernel from overriding this IRQ
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=218745
> Tested-by: Gianni <gianni.casagrande.mail@gmail.com>
> Signed-off-by: Tamim Khan <tamim@fusetak.com>
> ---
> drivers/acpi/resource.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
> index 59423fe9d0f2..23d6f5d4206f 100644
> --- a/drivers/acpi/resource.c
> +++ b/drivers/acpi/resource.c
> @@ -517,6 +517,13 @@ static const struct dmi_system_id irq1_level_low_skip_override[] = {
> DMI_MATCH(DMI_BOARD_NAME, "E1504GAB"),
> },
> },
> + {
> + /* Asus Vivobook Pro N6506MV */
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> + DMI_MATCH(DMI_BOARD_NAME, "N6506MV"),
> + },
> + },
> {
> /* LG Electronics 17U70P */
> .matches = {
> --
Applied as 6.10 material, thanks!
prev parent reply other threads:[~2024-04-30 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 17:08 [PATCH] ACPI: resource: Skip IRQ override on Asus Vivobook Pro N6506MV Tamim Khan
2024-04-30 19: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='CAJZ5v0jrw0frQPcMF94SWOSD=J4ktFyTo0jc1kuBKTsiHf-+Wg@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=gianni.casagrande.mail@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=tamim@fusetak.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).