Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: hongxing.zhu@oss.nxp.com
Cc: Frank.Li@kernel.org, imx@lists.linux.dev, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] PCI: dwc: Add suspend_poweroff flag for platforms with RC power loss
Date: Thu, 17 Sep 2026 06:34:56 +0000	[thread overview]
Message-ID: <20260917063457.0C6AA1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917063322.4102035-1-hongxing.zhu@oss.nxp.com>

> From: Richard Zhu <hongxing.zhu@nxp.com>
> 
> Some platforms like i.MX power off their PCIe RC controllers during
> system suspend, requiring full re-initialization on resume. These
> platforms need to enter L2 state to properly notify endpoints before
> power loss.
> 
> According to PCIe base spec r7.0, sec 5.2, the system software should
> transition the device into D3Hot before broadcasting the PME_Turn_Off
> message to initiate L2 entry. In practice, endpoint drivers properly
> put their devices into D3hot during the suspend flow. However, some
> wakeup-capable endpoint devices that don't support PME from D3cold
> fail the D3cold capability check in pci_host_common_d3cold_possible(),
> which currently prevents L2 entry even though the devices are already
> in the required D3hot state.
> 
> For platforms where the RC loses power during suspend, L2 entry is
> essential regardless of D3cold support, as the link will be lost anyway
> when the RC powers off. Without L2 entry, endpoints are not properly
> notified before power loss, which can cause issues during resume and
> reinitialization.
> 
> Add a suspend_poweroff flag to allow L2 entry for devices that are in
> D3hot but fail the D3cold capability check, and enable it for i.MX PCIe
> controllers that lose power during suspend.
> 
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917063322.4102035-1-hongxing.zhu@oss.nxp.com?part=1


      reply	other threads:[~2026-09-17  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  6:33 [PATCH v3] PCI: dwc: Add suspend_poweroff flag for platforms with RC power loss hongxing.zhu
2026-09-17  6:34 ` sashiko-bot [this message]

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=20260917063457.0C6AA1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=hongxing.zhu@oss.nxp.com \
    --cc=imx@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox