From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Quirk Intel DG2 ASPM L1 acceptable latency to be unlimited
Date: Tue, 5 Apr 2022 19:24:41 +0300 [thread overview]
Message-ID: <YkxtSRQxfWzxuCU5@lahna> (raw)
In-Reply-To: <20220405160151.GA68831@bhelgaas>
Hi Bjorn,
On Tue, Apr 05, 2022 at 11:01:51AM -0500, Bjorn Helgaas wrote:
> On Tue, Apr 05, 2022 at 12:38:10PM +0300, Mika Westerberg wrote:
> > Intel DG2 discrete graphics PCIe endpoints hard-code their acceptable L1
> > ASPM latency to be < 1us even though the hardware actually supports
> > higher latencies (> 64 us) just fine. In order to allow the links to go
> > into L1 and save power, quirk the acceptable L1 ASPM latency for these
> > endpoints to be unlimited.
>
> Is there a plan to fix this in future DG2 hardware/firmware?
> Obviously the point of Dev Cap is to make the device self-describing
> so we can avoid updates like this every time new hardware comes out.
Yes, I think that's the plan.
> > Note this does not have any effect unless the user requested the kernel
> > to enable ASPM in the first place (by default we don't enable it).
>
> I think this depends on the platform and kernel config, doesn't it?
> If CONFIG_PCIEASPM_POWERSAVE=y or CONFIG_PCIEASPM_POWER_SUPERSAVE=y
> I suspect we would enable ASPM L1 even without the parameters below.
>
> > This is done with "pcie_aspm=force pcie_aspm.policy=powersupsersave"
> > command line parameters.
>
> s/powersupsersave/powersupersave/
>
> This should affect "powersave" as well as "powersupersave", right?
> Both enable L1. "powersupersave" enables the L1 substates.
>
> We *should* be able to enable/disable ASPM L1 using the sysfs "l1_aspm
> file, too.
Indeed you are right. I think we can drop that paragraph completely from
the commit log. Do you want me to send v2 with that corrected or you
will do that while applying?
Thanks!
next prev parent reply other threads:[~2022-04-05 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 9:38 [PATCH] PCI: Quirk Intel DG2 ASPM L1 acceptable latency to be unlimited Mika Westerberg
2022-04-05 12:49 ` Rodrigo Vivi
2022-04-05 16:01 ` Bjorn Helgaas
2022-04-05 16:23 ` Vivi, Rodrigo
2022-04-05 16:24 ` Mika Westerberg [this message]
2022-04-07 17:06 ` Bjorn Helgaas
2022-04-08 6:44 ` Mika Westerberg
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=YkxtSRQxfWzxuCU5@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rodrigo.vivi@intel.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