From: Bjorn Helgaas <helgaas@kernel.org>
To: "Mario Limonciello (AMD)" <superm1@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH 0/5] Improvements to PCI hibernate path
Date: Mon, 27 Apr 2026 15:34:04 -0500 [thread overview]
Message-ID: <20260427203404.GA182096@bhelgaas> (raw)
In-Reply-To: <20260427035341.1425576-1-superm1@kernel.org>
On Sun, Apr 26, 2026 at 10:53:36PM -0500, Mario Limonciello (AMD) wrote:
> A few cycles ago I sent out a kernel series for using the S4 paths when
> the system goes to S5. Some parts of it got merged, and Rafael suggested
> to split the other parts into smaller pieces across multiple kernel cycles
> to make bisecting easier.
>
> This fell into my backlog behind other things, so I wanted to try again
> this cycle for the PCI pieces. I have been carrying it, rebasing it and
> personally using it for a while now though.
>
> This series attempts to unify the PCI suspend and hibernate paths and to
> fix some things that I observed to be wrong with how I expect hibernate
> to work.
>
> It is based off 7.1-rc1 + Lukas' patch:
> "PCI: Stop setting cached power state to "unknown" on unbind"
Hi Mario, would you mind posting a v2 that includes Lukas' patch, so
the whole series applies cleanly so Sashiko can go through it?
I already applied Lukas' patch on pci/pm, but I guess Sashiko can't
parse that dependency.
> Mario Limonciello (AMD) (5):
> PCI/PM: Disable device wakeups when halting or powering off system
> PCI/PM: Split out code from pci_pm_suspend_noirq() into helper
> PCI/PM: Run bridge power up actions as part of restore phase
> PCI/PM: Use pci_power_manageable() in pci_pm_poweroff_noirq()
> PCI: Put PCIe bridges with downstream devices into D3 at hibernate
>
> drivers/pci/pci-driver.c | 103 ++++++++++++++++++++++++++-------------
> 1 file changed, 69 insertions(+), 34 deletions(-)
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-04-27 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 3:53 [PATCH 0/5] Improvements to PCI hibernate path Mario Limonciello (AMD)
2026-04-27 3:53 ` [PATCH 1/5] PCI/PM: Disable device wakeups when halting or powering off system Mario Limonciello (AMD)
2026-04-27 3:53 ` [PATCH 2/5] PCI/PM: Split out code from pci_pm_suspend_noirq() into helper Mario Limonciello (AMD)
2026-04-27 3:53 ` [PATCH 3/5] PCI/PM: Run bridge power up actions as part of restore phase Mario Limonciello (AMD)
2026-04-27 3:53 ` [PATCH 4/5] PCI/PM: Use pci_power_manageable() in pci_pm_poweroff_noirq() Mario Limonciello (AMD)
2026-04-27 3:53 ` [PATCH 5/5] PCI: Put PCIe bridges with downstream devices into D3 at hibernate Mario Limonciello (AMD)
2026-04-27 12:20 ` [PATCH 0/5] Improvements to PCI hibernate path Rafael J. Wysocki
2026-04-27 14:14 ` Mario Limonciello
2026-04-27 15:09 ` Rafael J. Wysocki
2026-04-27 15:19 ` Mario Limonciello
2026-04-27 16:06 ` Rafael J. Wysocki
2026-04-27 20:34 ` Bjorn Helgaas [this message]
2026-04-27 20:36 ` Mario Limonciello
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=20260427203404.GA182096@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=rafael@kernel.org \
--cc=superm1@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