From: Chuanhong Guo <gch981213@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
"Limonciello, Mario" <mario.limonciello@amd.com>
Cc: linux-acpi@vger.kernel.org, stable@vger.kernel.org,
Tighe Donnelly <tighe.donnelly@protonmail.com>,
Kent Hou Man <knthmn0@gmail.com>, Len Brown <lenb@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] ACPI: skip IRQ1 override on 3 Ryzen 6000 laptops
Date: Fri, 1 Jul 2022 20:44:54 +0800 [thread overview]
Message-ID: <CAJsYDVL=fgExYdw3JB-59rCwOqTbSt2N0Xw2WCmoTSzOQEMRRg@mail.gmail.com> (raw)
In-Reply-To: <b84edc24-0a3a-a4d2-6481-fb3d4cee6dda@amd.com>
On Fri, Jul 1, 2022 at 4:12 AM Limonciello, Mario
<mario.limonciello@amd.com> wrote:
> However I do want to point out that Windows doesn't care about legacy
> format or not. This bug where keyboard doesn't work only popped up on
> Linux.
>
> Given the number of systems with the bug is appearing to grow I wonder
> if the right answer is actually a new heuristic that doesn't apply the
> kernel override for polarity inversion anymore. Maybe if the system is
> 2022 or newer? Or on the ACPI version?
The previous attempt to limit the scope of IRQ override ends up
breaking some other buggy devices:
https://patchwork.kernel.org/project/linux-acpi/patch/20210728151958.15205-1-hui.wang@canonical.com/
It's unfortunate that the original author of this IRQ override doesn't
limit the scope to their exact devices.
Hi, Rafael! What do you think? should we skip this IRQ override
one-by-one or add a different matching logic to check the bios date
instead?
--
Regards,
Chuanhong Guo
next prev parent reply other threads:[~2022-07-01 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 2:23 [PATCH v5] ACPI: skip IRQ1 override on 3 Ryzen 6000 laptops Chuanhong Guo
2022-06-30 20:12 ` Limonciello, Mario
2022-07-01 12:44 ` Chuanhong Guo [this message]
2022-07-05 18:24 ` Rafael J. Wysocki
2022-07-05 18:27 ` Limonciello, Mario
2022-07-05 18:31 ` Rafael J. Wysocki
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='CAJsYDVL=fgExYdw3JB-59rCwOqTbSt2N0Xw2WCmoTSzOQEMRRg@mail.gmail.com' \
--to=gch981213@gmail.com \
--cc=knthmn0@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tighe.donnelly@protonmail.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 NNTP newsgroup(s).