From: Shawn Lin <shawn.lin@rock-chips.com>
To: "Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>
Cc: shawn.lin@rock-chips.com, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v5 0/8] PCI: dw-rockchip: add system suspend support
Date: Tue, 24 Mar 2026 22:00:27 +0800 [thread overview]
Message-ID: <d07bf937-a8ad-ab89-77b2-c7d36e7952c9@rock-chips.com> (raw)
In-Reply-To: <20260316-rockchip-pcie-system-suspend-v5-0-5bb5ad37d643@collabora.com>
Hi Sebastian
在 2026/03/17 星期二 3:10, Sebastian Reichel 写道:
> I've recently been working on fixing up at least basic system suspend
> support on the Rockchip RK3576 platform. The last open issue is missing
> support in the PCIe driver. This series is a follow-up for Shawn Lin's
> series with feedback from Niklas Cassel and Manivannan Sadhasivam being
> handled as well as some of my own changes fixing up things I noticed.
>
> In opposite to Shawn Lin I did not test with different peripherals as my
> main goal is getting basic suspend to ram working in the first place. I
> did notice issues with the Broadcom WLAN card on the RK3576 EVB.
> Suspending that platform without a driver being probed works, but after
> probing brcmfmac suspend is aborted because brcmf_pcie_pm_enter_D3()
> does not work. As far as I can tell the problem is unrelated to the
> Rockchip PCIe driver.
Thanks for the patchset. It doesn't cleanly apply to new -rc now so I
assume it need a rebase. Anyway, I amended this series to apply them
to -rc5 and tested them on several platforms, it works fine.
However, I think patch 7 actually put the host and device into D3cold
unconditionly, with reset the controller,power-off 3v3 and deassert
perst# which doesn't follow NVMe's requirement at least.
Krishna is working on it [1], it would be better to follow the same
patten.
[1]
https://lore.kernel.org/all/20260217-d3cold-v2-0-89b322864043@oss.qualcomm.com/
>
> Changes since PATCHv4:
> * https://lore.kernel.org/r/20251029-rockchip-pcie-system-suspend-v4-0-ce2e1b0692d2@collabora.com
> * rebase to v7.0-rc1
> * Add an RFC patch at the end with some bits I found in the Rockchip vendor kernel;
> * Made some tests on Rock 5B+ (RK3588); with this patch series suspending works
> when setting pm_test to devices. A full system suspend fails in a later step,
> but that is independent of PCIe.
>
> Changes since PATCHv3:
> * https://lore.kernel.org/linux-pci/1744940759-23823-1-git-send-email-shawn.lin@rock-chips.com/
> * rename rockchip_pcie_get_ltssm to rockchip_pcie_get_ltssm_status_reg
> in a separate patch (Niklas Cassel)
> * rename rockchip_pcie_get_pure_ltssm to rockchip_pcie_get_ltssm_state
> in a separate patch (Niklas Cassel)
> * Move devm_phy_get out of phy_init to probe in a separate patch
> (Manivannan Sadhasivam)
> * Add helper function for enhanced LTSSM control mode in a separate patch
> (Niklas Cassel)
> * Add helper function for controller mode in a separate patch
> (Niklas Cassel)
> * Add helper function for DDL indicator in a separate patch
> (Niklas Cassel)
> * Move rockchip_pcie_pme_turn_off implementation in a separate patch
> * Rebase to v6.18-rc3 using new FIELD_PREP_WM16()
> * Improve readability of PME_TURN_OFF/PME_TO_ACK defines (Manivannan Sadhasivam)
> * Fix usage of reverse Xmas (Manivannan Sadhasivam)
> * Assert PERST# before turning off other resources (Manivannan Sadhasivam)
> * Improve some error messages (Manivannan Sadhasivam)
> * Rename goto labels as per their purpose (Manivannan Sadhasivam)
> * Add extra patch for dw_pcie_resume_noirq, since I've seen errors
> during resume on boards not having anything plugged into their PCIe
> port
>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
> Sebastian Reichel (8):
> PCI: dw-rockchip: Restore vpcie3v3 regulator handle
> PCI: dw-rockchip: Move devm_phy_get out of phy_init
> PCI: dw-rockchip: Add helper function for enhanced LTSSM control mode
> PCI: dw-rockchip: Add helper function for controller mode
> PCI: dw-rockchip: Add helper function for DDL indicator
> PCI: dw-rockchip: Add pme_turn_off support
> PCI: dw-rockchip: Add system PM support
> [RFC] PCI: dw-rockchip: port some suspend code from vendor kernel
>
> drivers/pci/controller/dwc/pcie-dw-rockchip.c | 242 ++++++++++++++++++++++----
> 1 file changed, 206 insertions(+), 36 deletions(-)
> ---
> base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
> change-id: 20251028-rockchip-pcie-system-suspend-86cf08a7b229
>
> Best regards,
prev parent reply other threads:[~2026-03-24 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 19:10 [PATCH v5 0/8] PCI: dw-rockchip: add system suspend support Sebastian Reichel
2026-03-16 19:10 ` [PATCH v5 1/8] PCI: dw-rockchip: Restore vpcie3v3 regulator handle Sebastian Reichel
2026-03-16 19:10 ` [PATCH v5 2/8] PCI: dw-rockchip: Move devm_phy_get out of phy_init Sebastian Reichel
2026-03-16 19:10 ` [PATCH v5 3/8] PCI: dw-rockchip: Add helper function for enhanced LTSSM control mode Sebastian Reichel
2026-03-16 19:10 ` [PATCH v5 4/8] PCI: dw-rockchip: Add helper function for controller mode Sebastian Reichel
2026-03-16 19:10 ` [PATCH v5 5/8] PCI: dw-rockchip: Add helper function for DDL indicator Sebastian Reichel
2026-03-16 19:10 ` [PATCH v5 6/8] PCI: dw-rockchip: Add pme_turn_off support Sebastian Reichel
2026-03-16 19:10 ` [PATCH v5 7/8] PCI: dw-rockchip: Add system PM support Sebastian Reichel
2026-03-16 19:10 ` [PATCH RFC v5 8/8] PCI: dw-rockchip: port some suspend code from vendor kernel Sebastian Reichel
2026-03-17 0:47 ` Shawn Lin
2026-03-24 14:00 ` Shawn Lin [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=d07bf937-a8ad-ab89-77b2-c7d36e7952c9@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=jingoohan1@gmail.com \
--cc=kernel@collabora.com \
--cc=kwilczynski@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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