From: sashiko-bot@kernel.org
To: "Francisco Beltrán Millalén" <fbeltranmillalen@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 1/3] usb: hcd-pci: Honour pci_save_state() failure
Date: Wed, 30 Sep 2026 14:26:36 +0000 [thread overview]
Message-ID: <20260930142636.A62A51F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260930141914.6678-2-fbeltranmillalen@gmail.com>
> hcd_pci_suspend_noirq() ignores the return value of pci_save_state() and
> goes on to pci_prepare_to_sleep().
>
> The next patch makes pci_save_state() fail, without marking the state as
> saved, when the config space of the device is not accessible. For such
> a controller pci_prepare_to_sleep() does not work either:
> pci_set_low_power_state() reads the PM control register as all ones and
> marks the device D3cold. pci_pm_suspend_noirq() then finds a device
> whose power state changed without its state being saved, and warns.
> With an earlier version of the next patch on a MacBookPro14,3, whose
> Thunderbolt xHCI controllers can be inaccessible at this point:
>
> xhci_hcd 0000:7d:00.0: PCI PM: State of device not saved by hcd_pci_suspend_noirq+0x0/0x180
> WARNING: CPU: 7 PID: 96793 at drivers/pci/pci-driver.c:888 pci_pm_suspend_noirq+0x2f4/0x300
>
> [ ... ]
> in D0 instead of being put into a low-power state with an incomplete
> saved state.
>
> Assisted-by: LLM
> Signed-off-by: Francisco Beltrán Millalén <fbeltranmillalen@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930141914.6678-1-fbeltranmillalen@gmail.com?part=1
next prev parent reply other threads:[~2026-09-30 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 14:19 [PATCH v2 0/3] PCI/PM: Do not save the config space of an inaccessible device Francisco Beltrán Millalén
2026-09-30 14:19 ` [PATCH v2 1/3] usb: hcd-pci: Honour pci_save_state() failure Francisco Beltrán Millalén
2026-09-30 14:26 ` sashiko-bot [this message]
2026-09-30 14:19 ` [PATCH v2 2/3] PCI/PM: Do not save the config space of an inaccessible device Francisco Beltrán Millalén
2026-09-30 14:29 ` sashiko-bot
2026-10-08 22:58 ` Bjorn Helgaas
2026-10-09 2:41 ` Francisco Beltrán Millalén
2026-10-09 17:08 ` Farhan Ali
2026-10-11 21:04 ` Francisco Beltrán Millalén
2026-09-30 14:19 ` [PATCH v2 3/3] PCI: Do not mistake an absent device for an active link Francisco Beltrán Millalén
2026-09-30 14:27 ` sashiko-bot
2026-10-08 18:55 ` [PATCH v2 0/3] PCI/PM: Do not save the config space of an inaccessible device Darrell Gum
2026-10-08 22:34 ` Bjorn Helgaas
2026-10-09 2:40 ` Francisco Beltrán Millalén
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=20260930142636.A62A51F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=fbeltranmillalen@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.