public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kenneth R. Crudup" <kenny@panix.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: vidyas@nvidia.com, bhelgaas@google.com,
	kai.heng.feng@canonical.com, andrea.righi@canonical.com,
	vicamo.yang@canonical.com,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Kuppuswamy Sathyanarayanan"
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	"David E . Box" <david.e.box@linux.intel.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Ricky WU" <ricky_wu@realtek.com>,
	"Mario Limonciello" <mario.limonciello@amd.com>,
	linux-pm@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: My AlderLake Dell (XPS-9320) needs these patches to get full standby/low-power modes
Date: Wed, 8 Nov 2023 07:44:31 -0800 (PST)	[thread overview]
Message-ID: <f3dd694b-8d9-ef-9d21-ad4394f6e33@panix.com> (raw)
In-Reply-To: <20231106181107.GA255535@bhelgaas>


On Mon, 6 Nov 2023, Bjorn Helgaas wrote:

> > I'd bisected it to the following commits (in this order):
> > 4ff116d0d5fd PCI/ASPM: Save L1 PM Substates Capability for suspend/resume
> > 5e85eba6f50d PCI/ASPM: Refactor L1 PM Substates Control Register programming
> > 1a0102a08f20 UBUNTU: SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain
> > 47c7bfd31514 UBUNTU: SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD
> > 154d48da2c57 UBUNTU: SAUCE: vmd: fixup bridge ASPM by driver name instead

> Thanks for these.  You don't happen to have URLs for those Ubuntu
> commits, do you?

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar/commit/?id=1a0102a08f206149d9abd56c2b28877c878b5526
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar/commit/?id=47c7bfd31514e7b54a1f830f7707297aebbb8679
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar/commit/?id=154d48da2c57514e4b5dadc7b8c70a4edb550981

> Thank you very much for raising this again.

They've been really great for battery life on my laptop, so I'd like to help
these in some form get upstreamed (provided there's no bad side-effects, of
course).

	-Kenny

-- 
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA

  parent reply	other threads:[~2023-11-08 16:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <218aa81f-9c6-5929-578d-8dc15f83dd48@panix.com>
2023-11-06 18:11 ` My AlderLake Dell (XPS-9320) needs these patches to get full standby/low-power modes 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 [this message]
     [not found] <402b2e32-3b54-4e80-92fd-9237549ffa14@panix.com>
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=f3dd694b-8d9-ef-9d21-ad4394f6e33@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=ilpo.jarvinen@linux.intel.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=ricky_wu@realtek.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --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