From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Chuanhong Guo <gch981213@gmail.com>
Cc: linux-acpi@vger.kernel.org, rafael@kernel.org,
linux-kernel@vger.kernel.org, ofenfisch@googlemail.com,
wse@tuxedocomputers.com, adam.niederer@gmail.com,
adrian@freund.io, jirislaby@kernel.org,
Renjith.Pananchikkal@amd.com, anson.tsao@amd.com,
Richard.Gong@amd.com, evilsnoo@proton.me,
ruinairas1992@gmail.com, nmschulte@gmail.com
Subject: Re: [PATCH v3] ACPI: resource: Remove "Zen" specific match and quirks
Date: Mon, 5 Jun 2023 09:46:31 -0500 [thread overview]
Message-ID: <9d420293-f5af-7563-e7ec-1e42bd69bb8e@amd.com> (raw)
In-Reply-To: <CAJsYDVKoB1AEL47Ud+8jbxMrbZedM0i9p44-PLQTFR9PKLfy6A@mail.gmail.com>
On 6/3/2023 5:19 AM, Chuanhong Guo wrote:
> Hi!
>
> On Fri, Jun 2, 2023 at 6:12 AM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>> commit 9946e39fe8d0 ("ACPI: resource: skip IRQ override on
>> AMD Zen platforms") attempted to overhaul the override logic so it
>> didn't apply on X86 AMD Zen systems. This was intentional so that
>> systems would prefer DSDT values instead of default MADT value for
>> IRQ 1 on Ryzen 6000 systems which typically uses ActiveLow for IRQ1.
>>
>> This turned out to be a bad assumption because several vendors
>> add Interrupt Source Override but don't fix the DSDT. A pile of
>> quirks was collecting that proved this wasn't sustaintable.
>>
>> Furthermore some vendors have used ActiveHigh for IRQ1.
>> To solve this problem revert the following commits:
>> * commit 17bb7046e7ce ("ACPI: resource: Do IRQ override on all TongFang
>> GMxRGxx")
>> * commit f3cb9b740869 ("ACPI: resource: do IRQ override on Lenovo 14ALC7")
>> * commit bfcdf58380b1 ("ACPI: resource: do IRQ override on LENOVO IdeaPad")
>> * commit 7592b79ba4a9 ("ACPI: resource: do IRQ override on XMG Core 15")
>> * commit 9946e39fe8d0 ("ACPI: resource: skip IRQ override on AMD Zen
>> platforms")
>>
>> Cc: ofenfisch@googlemail.com
>> Cc: wse@tuxedocomputers.com
>> Cc: adam.niederer@gmail.com
>> Cc: adrian@freund.io
>> Cc: jirislaby@kernel.org
>> Cc: Renjith.Pananchikkal@amd.com
>> Cc: anson.tsao@amd.com
>> Cc: Richard.Gong@amd.com
>> Cc: Chuanhong Guo <gch981213@gmail.com>
>> Reported-by: evilsnoo@proton.me
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217394
>> Reported-by: ruinairas1992@gmail.com
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217406
>> Reported-by: nmschulte@gmail.com
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217336
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>> ---
>> v2->v3:
>> * Adjust to drop heuristics entirely
>> * Drop tested tags
>> * Add more links and people to Cc
>> * Drop Fixes tag as this got a lot more risky
>> v1->v2:
>> * Rebase on 71a485624c4c ("ACPI: resource: Add IRQ override quirk for LG UltraPC 17U70P")
>> * Pick up tag
>>
>> Rafael,
>> Please hold off on picking this up until the majority of those on CC
>> have tested it on hardware they have and reported results.
>>
>> Everyone else,
>> Please test. If you have problems with this applied, please share
>> an acpidump and dmesg either on a bug or to me privately.
> I was expecting this patch to break my keyboard again but
> that didn't happen. I'm on the latest UEFI from Lenovo.
> By dumping ACPI APIC I found that there's this:
>
> [0C4h 0196 1] Subtable Type : 02 [Interrupt Source Override]
> [0C5h 0197 1] Length : 0A
> [0C6h 0198 1] Bus : 00
> [0C7h 0199 1] Source : 01
> [0C8h 0200 4] Interrupt : 00000001
> [0CCh 0204 2] Flags (decoded below) : 0007
> Polarity : 3
> Trigger Mode : 1
>
> I don't have a dump of the ACPI table from older UEFIs anymore.
>
> Tested on Lenovo Thinkbook 14G4+ ARA with the latest
> UEFI (J6CN45WW).
>
> Tested-by: Chuanhong Guo <gch981213@gmail.com>
Thanks! Yours is the one I was most worried about.
next prev parent reply other threads:[~2023-06-05 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 22:11 Mario Limonciello
2023-06-02 15:34 ` Werner Sembach
2023-06-03 9:54 ` Nathan Schulte
2023-06-03 10:19 ` Chuanhong Guo
2023-06-05 14:46 ` Limonciello, Mario [this message]
2023-06-05 17:21 ` 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=9d420293-f5af-7563-e7ec-1e42bd69bb8e@amd.com \
--to=mario.limonciello@amd.com \
--cc=Renjith.Pananchikkal@amd.com \
--cc=Richard.Gong@amd.com \
--cc=adam.niederer@gmail.com \
--cc=adrian@freund.io \
--cc=anson.tsao@amd.com \
--cc=evilsnoo@proton.me \
--cc=gch981213@gmail.com \
--cc=jirislaby@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmschulte@gmail.com \
--cc=ofenfisch@googlemail.com \
--cc=rafael@kernel.org \
--cc=ruinairas1992@gmail.com \
--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
all inboxes | Powered by JetHome®