public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Kenneth Crudup <kenny@panix.com>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>,
	vidyas@nvidia.com, bhelgaas@google.com,
	andrea.righi@canonical.com, vicamo.yang@canonical.com,
	linux-pm@vger.kernel.org
Subject: Re: My AlderLake Dell (XPS-9320) needs these patches to get full standby/low-power modes
Date: Thu, 12 Dec 2024 14:56:12 -0600	[thread overview]
Message-ID: <20241212205612.GA3368300@bhelgaas> (raw)
In-Reply-To: <b720f20b-ff2f-4646-b263-8597fb3b342f@panix.com>

On Wed, Dec 11, 2024 at 03:26:37PM -0800, Kenneth Crudup wrote:
> 
> So we're on 6.13-rc2 and the patches are getting closer and closer, but they
> still need to be manually added.
> 
> The good news is now only (variants of) "PCI/ASPM: Enable LTR for endpoints
> behind VMD" and "PCI/ASPM: Enable ASPM for links under VMD domain" are
> needed.

Do you have lore links for these handy?  I'm not sure exactly what to
look at.

https://lore.kernel.org/linux-pci/?q=s%3A%22Enable+LTR+for+endpoints+behind+VMD%22
didn't find anything.

https://lore.kernel.org/linux-pci/?q=s%3A%22Enable+ASPM+for+links+under+VMD+domain%22
found
https://lore.kernel.org/linux-pci/20200821123222.32093-1-kai.heng.feng@canonical.com/t/#u,
but it's four years old.

  reply	other threads:[~2024-12-12 20:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04 17:13 My AlderLake Dell (XPS-9320) needs these patches to get full standby/low-power modes Kenneth R. Crudup
2023-11-06 18:11 ` Bjorn Helgaas
2023-11-07 11:15   ` Mika Westerberg
2023-11-16 20:10     ` David E. Box
2023-11-16 23:18       ` Bjorn Helgaas
2023-11-16 23:27         ` Matthew Garrett
2023-11-18  0:21         ` David E. Box
2023-12-21  1:19           ` David E. Box
2023-12-27  0:03             ` Bjorn Helgaas
2024-05-13  5:23               ` Kenneth R. Crudup
2023-11-08 15:44   ` Kenneth R. Crudup
2023-11-08 11:45 ` Kai-Heng Feng
2023-11-08 15:46   ` Kenneth R. Crudup
2024-03-12  2:37 ` Kenneth R. Crudup
2024-03-21 10:12   ` Kai-Heng Feng
2024-07-15 18:27     ` Kenneth Crudup
2024-07-17  1:59       ` Kai-Heng Feng
2024-07-17  3:39         ` Kenneth Crudup
2024-07-17  4:40           ` Kenneth Crudup
2024-07-17 23:46         ` Kenneth Crudup
2024-12-11 23:26           ` Kenneth Crudup
2024-12-12 20:56             ` Bjorn Helgaas [this message]
2024-12-12 23:04               ` Kenneth Crudup
2024-12-12 23:13                 ` Kenneth Crudup
2024-12-13 16:43                 ` Bjorn Helgaas
2024-12-13 19:48                   ` Kenneth Crudup
2024-12-13 20:27                     ` Kenneth Crudup
2024-12-13 22:26                       ` Kenneth Crudup
2024-12-13 22:33                         ` Kenneth Crudup
2024-12-13 23:02                         ` Bjorn Helgaas
2024-12-19 16:25                           ` David E. Box
2024-12-19 18:17                             ` Kenneth Crudup
2024-12-19 19:52                               ` David E. Box
2024-12-19 20:37                                 ` Kenneth Crudup

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=20241212205612.GA3368300@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=andrea.righi@canonical.com \
    --cc=bhelgaas@google.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=kenny@panix.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=vicamo.yang@canonical.com \
    --cc=vidyas@nvidia.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