From: "Kenneth R. Crudup" <kenny@panix.com>
To: "David E. Box" <david.e.box@linux.intel.com>
Cc: rafael@kernel.org, bhelgaas@google.com,
vicamo.yang@canonical.com, ilpo.jarvinen@linux.intel.com,
nirmal.patel@linux.intel.com, linux-pm@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Kenneth R. Crudup" <kenny@panix.com>
Subject: Re: [RFC 0/2] PCI/ASPM: Allow controller-defined default link state
Date: Wed, 16 Jul 2025 23:12:45 -0700 (PDT) [thread overview]
Message-ID: <7a229e18-fbfd-8652-ec2e-a3a3273f7fac@panix.com> (raw)
In-Reply-To: <20250717004034.2998443-1-david.e.box@linux.intel.com>
Unfortunately, having tested the patch (against Linus' master), it doesn't work.
I don't think the ASPM(?) state is making it to the VMD.
LMK if you need more info.
-Kenny
On Wed, 16 Jul 2025, David E. Box wrote:
> Testing is appreciated as I didn't get a chance to do so yet but plan to.
> Thanks, David
>
> ---
>
> David E. Box (2):
> PCI/ASPM: Allow drivers to provide ASPM link state via pci_bus
> PCI: vmd: Provide default ASPM link state for synthetic hierarchy
>
> drivers/pci/controller/vmd.c | 7 +++++--
> drivers/pci/pcie/aspm.c | 5 ++++-
> include/linux/pci.h | 12 ++++++++----
> 3 files changed, 17 insertions(+), 7 deletions(-)
>
>
> base-commit: d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af
>
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA
next prev parent reply other threads:[~2025-07-17 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 0:40 David E. Box
2025-07-17 0:40 ` [RFC 1/2] PCI/ASPM: Allow drivers to provide ASPM link state via pci_bus David E. Box
2025-07-17 10:00 ` Rafael J. Wysocki
2025-07-17 0:40 ` [RFC 2/2] PCI: vmd: Provide default ASPM link state for synthetic hierarchy David E. Box
2025-07-17 6:12 ` Kenneth R. Crudup [this message]
2025-07-17 6:57 ` [RFC 0/2] PCI/ASPM: Allow controller-defined default link state Manivannan Sadhasivam
2025-07-17 14:03 ` David Box
2025-07-17 6:55 ` Manivannan Sadhasivam
2025-07-17 10:03 ` Rafael J. Wysocki
2025-07-17 14:13 ` David Box
2025-07-17 15:37 ` Rafael J. Wysocki
2025-07-17 17:49 ` David 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=7a229e18-fbfd-8652-ec2e-a3a3273f7fac@panix.com \
--to=kenny@panix.com \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nirmal.patel@linux.intel.com \
--cc=rafael@kernel.org \
--cc=vicamo.yang@canonical.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®