From: Kenneth Crudup <kenny@panix.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Me <kenny@panix.com>
Cc: Russell Haley <yumpusamongus@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-pm@vger.kernel.org,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Vidya Sagar <vidyas@nvidia.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Andrea Righi <andrea.righi@canonical.com>,
You-Sheng Yang <vicamo.yang@canonical.com>,
linux-pci@vger.kernel.org,
Sergey Dolgov <sergey.v.dolgov@gmail.com>,
Nirmal Patel <nirmal.patel@linux.intel.com>,
Jonathan Derrick <jonathan.derrick@linux.dev>,
Jian-Hong Pan <jhp@endlessos.org>,
"David E. Box" <david.e.box@linux.intel.com>
Subject: Re: Raphael, I'd like your help upstreaming this VMD power-saving patch, please
Date: Fri, 23 May 2025 13:49:37 -0700 [thread overview]
Message-ID: <c8746066-b5cf-4582-83d1-02ca28fe4c38@panix.com> (raw)
In-Reply-To: <CAJZ5v0hWAbwtvZm4WrFc06v79JEpTVQ9KeHPuzVkvm5Vp9gK3Q@mail.gmail.com>
On 5/23/25 12:44, Rafael J. Wysocki wrote:
> I would try to replace the PCIE_LINK_STATE_ASPM_ALL in the patch with
>
> PCIE_LINK_STATE_L0S | PCIE_LINK_STATE_L1 | PCIE_LINK_STATE_L1_1 |
> PCIE_LINK_STATE_L1_1_PCIPM
I could get "Pkg%pc8" with these but no deeper until I'd added
"PCIE_LINK_STATE_L1_2" to the mix.
(I didn't see any power regressions after that (including
suspend/resume, but I didn't try for a longer time), so didn't re-add
"PCIE_LINK_STATE_L1_2_PCIPM", so that one may not be needed.)
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
prev parent reply other threads:[~2025-05-23 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 20:10 Raphael, I'd like your help upstreaming this VMD power-saving patch, please Kenneth R. Crudup
2025-05-12 21:09 ` Bjorn Helgaas
2025-05-12 22:41 ` Kenneth Crudup
2025-05-15 1:23 ` Russell Haley
2025-05-23 19:21 ` Kenneth Crudup
2025-05-23 19:44 ` Rafael J. Wysocki
2025-05-23 20:49 ` Kenneth Crudup [this message]
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=c8746066-b5cf-4582-83d1-02ca28fe4c38@panix.com \
--to=kenny@panix.com \
--cc=andrea.righi@canonical.com \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=jhp@endlessos.org \
--cc=jonathan.derrick@linux.dev \
--cc=kai.heng.feng@canonical.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nirmal.patel@linux.intel.com \
--cc=rafael@kernel.org \
--cc=sergey.v.dolgov@gmail.com \
--cc=vicamo.yang@canonical.com \
--cc=vidyas@nvidia.com \
--cc=yumpusamongus@gmail.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