From: Shawn Lin <shawn.lin@rock-chips.com>
To: Chukun Pan <amadeus@jmu.edu.cn>, Heiko Stuebner <heiko@sntech.de>
Cc: shawn.lin@rock-chips.com, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: Add Radxa E54C
Date: Sun, 11 Oct 2026 11:14:27 +0800 [thread overview]
Message-ID: <4903cefa-4926-4bae-93e9-1165bb9ae646@rock-chips.com> (raw)
In-Reply-To: <20260820100020.3370385-3-amadeus@jmu.edu.cn>
Hi Chukun
在 2026/08/20 星期四 18:00, Chukun Pan 写道:
> The Radxa E54C is a high-performance network computer with
> the Rockchip RK3582 SoC. It has the following features:
>
...
> +
> + vcc3v3_pcie: regulator-3v3-pcie {
> + compatible = "regulator-fixed";
> + regulator-name = "vcc3v3_pcie";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + vin-supply = <&vcc_sysin>;
> + };
> +
I was checking all PCIe part of rockchip dts files and wondered why it's
marked as an always-on regulator. But if it's actually not, it'd be
better to improve it later. That would make reset rootport mechanism
work better.
next prev parent reply other threads:[~2026-10-11 3:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 10:00 [PATCH v2 0/2] " Chukun Pan
2026-08-20 10:00 ` [PATCH v2 1/2] dt-bindings: arm: " Chukun Pan
2026-08-20 10:00 ` [PATCH v2 2/2] arm64: dts: " Chukun Pan
2026-10-11 3:14 ` Shawn Lin [this message]
2026-10-12 6:40 ` Chukun Pan
2026-10-12 6:55 ` Shawn Lin
2026-10-09 6:40 ` [PATCH v2 0/2] " Chukun Pan
2026-10-10 12:10 ` Heiko Stuebner
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=4903cefa-4926-4bae-93e9-1165bb9ae646@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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
all inboxes | Powered by JetHome®