From: sashiko-bot@kernel.org
To: "Shawn Lin" <shawn.lin@rock-chips.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 1/2] PCI: dw-rockchip: Power on devices below the RC using pwrctrl
Date: Thu, 29 Oct 2026 02:46:18 +0000 [thread overview]
Message-ID: <sashiko-outbox-188645@kernel.org> (raw)
In-Reply-To: <20261029024006.3483210-2-shawn.lin@rock-chips.com>
> Devices below the Rockchip PCIe host controller may need resources
> (regulators, clocks) enabled before they can be detected on the bus. So
> far the driver only enabled a single vpcie3v3 supply described by the
> controller node itself, which cannot express per-device or per-slot
> supplies.
>
> Use the PCI pwrctrl framework: before initializing the PHY, create the
> pwrctrl devices for the DT nodes below the controller and power them on.
> The supplies of the slot must be up before PHY init, so this has to run
> ahead of rockchip_pcie_phy_init().
>
> The controller node supply is kept for backward compatibility: boards
> that still describe vpcie3v3 on the controller keep working, and boards
> that move the supply into a child node get it enabled by pwrctrl.
>
> Only the RC mode is affected, the endpoint does not own the supplies of
> the devices below it.
>
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261029024006.3483210-1-shawn.lin@rock-chips.com?part=1
next prev parent reply other threads:[~2026-10-29 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 2:40 [PATCH v2 0/2] Manage the PCIe supplies with pwrctrl Shawn Lin
2026-10-29 2:40 ` [PATCH v2 1/2] PCI: dw-rockchip: Power on devices below the RC using pwrctrl Shawn Lin
2026-10-29 2:46 ` sashiko-bot [this message]
2026-10-29 2:40 ` [PATCH v2 2/2] arm64: dts: rockchip: rk3588-evb1: describe the PCIe3x4 slot supply Shawn Lin
2026-10-29 2:49 ` sashiko-bot
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=sashiko-outbox-188645@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=shawn.lin@rock-chips.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