From: You-Sheng Yang <vicamo.yang@canonical.com>
To: "David E. Box" <david.e.box@linux.intel.com>
Cc: michael.a.bottini@intel.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, me@adhityamohan.in,
rafael@kernel.org, hch@infradead.org, robh@kernel.org,
bhelgaas@google.com, kw@linux.com, lorenzo.pieralisi@arm.com,
nirmal.patel@linux.intel.com, jonathan.derrick@linux.dev
Subject: Re: [PATCH V8 0/4] PCI: vmd: Enable PCIe ASPM and LTR on select hardware
Date: Wed, 23 Nov 2022 18:27:18 +0800 [thread overview]
Message-ID: <5c766840-e092-45ea-0664-7bbdb78b933a@canonical.com> (raw)
In-Reply-To: <20221103021822.308586-1-david.e.box@linux.intel.com>
Hi David,
On 11/3/22 10:18, David E. Box wrote:
> This series adds a work around for enabling PCIe ASPM and for setting PCIe
> LTR values on VMD reserved root ports on select platforms. While
> configuration of these capabilities is usually done by BIOS, on these
> platforms these capabilities will not be configured because the ports are
> not visible to BIOS. This was part of an initial design that expected the
> driver to completely handle the ports, including power management. However
> on Linux those ports are still managed by the PCIe core, which has the
> expectation that they adhere to device standards including BIOS
> configuration, leading to this problem.
>
> The target platforms are Tiger Lake, Alder Lake, and Raptor Lake though the
> latter has already implemented support for configuring the LTR values.
> Meteor Lake is expected add BIOS ASPM support, eliminating the future need
> for this work around.
It appears to me that this patch series works only on Tiger Lake. We
have tried to revert our current work-arounds in Ubuntu kernels
generic-5.15/oem-5.17/oem-6.0/unstable-6.1 and apply this series, the
prebuilt kernels can be found in:
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1996620
However, only TGL can still enter PC10 as before.
ADL-M, RPL platforms will stay in PC3 with vmd LTR set, but ASPM
disabled. i915 RC6 blocked, too:
$ sudo cat /sys/kernel/debug/dri/
0/i915_dmc_info
...
DC3CO count: 0
DC3 -> DC5 count: 100
DC5 -> DC6 count: 0
> Note, the driver programs the LTRs because BIOS would also normally do this
> for devices that do not set them by default. Without this, SoC power
> management would be blocked on those platform. This SoC specific value is
> the maximum latency required to allow the SoC to enter the deepest power
> state.
>
> This patch addresses the following open bugzillas on VMD enabled laptops
> that cannot enter low power states.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=212355
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=215063
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=213717
>
> David E. Box (3):
> PCI: vmd: Use PCI_VDEVICE in device list
> PCI: vmd: Create feature grouping for client products
> PCI: vmd: Add quirk to configure PCIe ASPM and LTR
>
> Michael Bottini (1):
> PCI/ASPM: Add pci_enable_link_state()
>
> drivers/pci/controller/vmd.c | 96 ++++++++++++++++++++++++++----------
> drivers/pci/pcie/aspm.c | 54 ++++++++++++++++++++
> include/linux/pci.h | 7 +++
> 3 files changed, 131 insertions(+), 26 deletions(-)
>
>
> base-commit: 247f34f7b80357943234f93f247a1ae6b6c3a740
Regards,
You-Sheng Yang
next prev parent reply other threads:[~2022-11-23 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 2:18 [PATCH V8 0/4] PCI: vmd: Enable PCIe ASPM and LTR on select hardware David E. Box
2022-11-03 2:18 ` [PATCH V8 1/4] PCI/ASPM: Add pci_enable_link_state() David E. Box
2022-11-03 2:18 ` [PATCH V8 2/4] PCI: vmd: Use PCI_VDEVICE in device list David E. Box
2022-11-03 2:18 ` [PATCH V8 3/4] PCI: vmd: Create feature grouping for client products David E. Box
2022-11-03 2:18 ` [PATCH V8 4/4] PCI: vmd: Add quirk to configure PCIe ASPM and LTR David E. Box
2022-11-23 10:27 ` You-Sheng Yang [this message]
2022-11-23 16:09 ` [PATCH V8 0/4] PCI: vmd: Enable PCIe ASPM and LTR on select hardware David E. Box
2022-11-24 16:39 ` You-Sheng Yang
2022-12-07 9:05 ` Luke Jones
2022-12-08 2:40 ` David E. Box
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=5c766840-e092-45ea-0664-7bbdb78b933a@canonical.com \
--to=vicamo.yang@canonical.com \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=hch@infradead.org \
--cc=jonathan.derrick@linux.dev \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=me@adhityamohan.in \
--cc=michael.a.bottini@intel.com \
--cc=nirmal.patel@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
/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