From: Mario Limonciello <superm1@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
"open list:RADEON and AMDGPU DRM DRIVERS"
<amd-gfx@lists.freedesktop.org>,
"open list:HIBERNATION (aka Software Suspend,
aka swsusp)" <linux-pm@vger.kernel.org>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>,
"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list:SCSI SUBSYSTEM" <linux-scsi@vger.kernel.org>,
"open list:USB SUBSYSTEM" <linux-usb@vger.kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH v4 0/5] Improvements to S5 power consumption
Date: Thu, 3 Jul 2025 22:01:30 -0400 [thread overview]
Message-ID: <8fda8cf1-1291-422e-bb63-094e38c47b7b@kernel.org> (raw)
In-Reply-To: <CAJZ5v0jc-tjs_a+RCzu6bvrbfhv5QHqsWx-zKjH0wpisiJciKA@mail.gmail.com>
On 7/3/25 10:29, Rafael J. Wysocki wrote:
> On Mon, Jun 16, 2025 at 7:50 PM Mario Limonciello <superm1@kernel.org> wrote:
>>
>> From: Mario Limonciello <mario.limonciello@amd.com>
>>
>> A variety of issues both in function and in power consumption have been
>> raised as a result of devices not being put into a low power state when
>> the system is powered off.
>>
>> There have been some localized changes[1] to PCI core to help these issues,
>> but they have had various downsides.
>>
>> This series instead tries to use the S4 flow when the system is being
>> powered off. This lines up the behavior with what other operating systems
>> do as well. If for some reason that fails or is not supported, unwind and
>> do the previous S5 flow that will wake all devices and run their shutdown()
>> callbacks.
>
> I actually like this approach, but I think that it is risky.
Yeah; it does touch a lot of areas.
>
> It also requires more work/review from other people.
I view patches 3-5 as being dependent upon patch 1, so until we have
agreement on that one the others might not make a lot of sense.
Bjorn,
Can you take a look at patch 2?
>
> I'll be sending some comments on the individual patches going forward,
> but I think the earliest it can go in is after 6.17-rc1 (given it is
> reviewed properly till then).
Thanks!
>
> Thanks!
>
>> v3->v4:
>> * Fix LKP robot failure
>> * Rebase on v6.16-rc2
>>
>> Previous submissions [1]:
>> Link: https://lore.kernel.org/linux-pm/CAJZ5v0hrKEJa8Ad7iiAvQ3d_0ysVhzZcXSYc5kkL=6vtseF+bg@mail.gmail.com/T/#m91e4eae868a7405ae579e89b135085f4906225d2
>> Link: https://lore.kernel.org/linux-pci/20250506041934.1409302-1-superm1@kernel.org/
>> Link: https://lore.kernel.org/linux-pci/20231213182656.6165-1-mario.limonciello@amd.com/ (v1)
>> Link: https://lore.kernel.org/linux-pm/20250514193406.3998101-1-superm1@kernel.org/ (v2)
>> Link: https://lore.kernel.org/linux-pm/20250609024619.407257-1-superm1@kernel.org/ (v3)
>>
>> Mario Limonciello (5):
>> PM: Use hibernate flows for system power off
>> PCI: Put PCIe ports with downstream devices into D3 at hibernate
>> drm/amd: Avoid evicting resources at S5
>> scsi: Add PM_EVENT_POWEROFF into suspend callbacks
>> usb: sl811-hcd: Add PM_EVENT_POWEROFF into suspend callbacks
>>
>> drivers/base/power/main.c | 7 ++
>> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 4 +
>> drivers/pci/pci-driver.c | 94 ++++++++++++++--------
>> drivers/scsi/mesh.c | 1 +
>> drivers/scsi/stex.c | 1 +
>> drivers/usb/host/sl811-hcd.c | 1 +
>> include/linux/pm.h | 3 +
>> include/trace/events/power.h | 3 +-
>> kernel/reboot.c | 6 ++
>> 9 files changed, 86 insertions(+), 34 deletions(-)
>>
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2025-07-04 2:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 17:50 [PATCH v4 0/5] Improvements to S5 power consumption Mario Limonciello
2025-06-16 17:50 ` [PATCH v4 1/5] PM: Use hibernate flows for system power off Mario Limonciello
2025-06-16 17:50 ` [PATCH v4 2/5] PCI: Put PCIe ports with downstream devices into D3 at hibernate Mario Limonciello
2025-07-17 21:55 ` Bjorn Helgaas
2025-07-17 22:07 ` Mario Limonciello
2025-07-17 22:35 ` Ville Syrjälä
2025-06-16 17:50 ` [PATCH v4 3/5] drm/amd: Avoid evicting resources at S5 Mario Limonciello
2025-07-17 19:10 ` Alex Deucher
2025-06-16 17:50 ` [PATCH v4 4/5] scsi: Add PM_EVENT_POWEROFF into suspend callbacks Mario Limonciello
2025-06-16 17:50 ` [PATCH v4 5/5] usb: sl811-hcd: " Mario Limonciello
2025-07-03 14:29 ` [PATCH v4 0/5] Improvements to S5 power consumption Rafael J. Wysocki
2025-07-04 2:01 ` Mario Limonciello [this message]
2025-07-28 8:45 ` Eric Naim
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=8fda8cf1-1291-422e-bb63-094e38c47b7b@kernel.org \
--to=superm1@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bhelgaas@google.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=martin.petersen@oracle.com \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).