public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH 0/5] Improvements to PCI hibernate path
Date: Mon, 27 Apr 2026 09:14:29 -0500	[thread overview]
Message-ID: <ca274454-b58b-4837-a3fd-14ef30c24510@kernel.org> (raw)
In-Reply-To: <CAJZ5v0jMBpXC5BxjdMgpg8tMKpS3Hf2MO_MGNtdS_S+s41jx+A@mail.gmail.com>

On 4/27/26 07:20, Rafael J. Wysocki wrote:
> On Mon, Apr 27, 2026 at 5:53 AM Mario Limonciello (AMD)
> <superm1@kernel.org> 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"
>>
>> 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(-)
>>
>> --
> 
> It would be good to CC this to linux-pm.

Sure thing - if there is a need for a v2, I will include linux-pm in CC.

  reply	other threads:[~2026-04-27 14:14 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 [this message]
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
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=ca274454-b58b-4837-a3fd-14ef30c24510@kernel.org \
    --to=superm1@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 \
    /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