[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220714045613.GA8720@srcf.ucam.org>
Date: Thu, 14 Jul 2022 05:56:13 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Kai-Heng Feng <kai.heng.feng@...onical.com>
Cc: Bjorn Helgaas <helgaas@...nel.org>,
Manyi Li <limanyi@...ontech.com>, bhelgaas@...gle.com,
refactormyself@...il.com, kw@...ux.com, rajatja@...gle.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Vidya Sagar <vidyas@...dia.com>
Subject: Re: [PATCH] PCI/ASPM: Should not report ASPM support to BIOS if FADT
indicates ASPM is unsupported
On Thu, Jul 14, 2022 at 11:20:26AM +0800, Kai-Heng Feng wrote:
> According to commit 387d37577fdd ("PCI: Don't clear ASPM bits when the
> FADT declares it's unsupported"), the bit means "just use the ASPM
Yes, the assumption is that if the BIOS set up ASPM but FADT indicates
it's unsupported, just trust that the BIOS did the right thing and don't
interfere. It's been a long time, but when we were clearing the ASPM
bits in response to this FADT setting, a bunch of machines suddenly
started consuming a lot more power than when running Windows.
Powered by blists - more mailing lists