From: Shawn Lin <shawn.lin@rock-chips.com>
To: Bob Hui <bg9oxa@163.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: shawn.lin@rock-chips.com, Andrew Lunn <andrew@lunn.ch>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
sashiko-bot <sashiko-bot@kernel.org>
Subject: Re: [PATCH v8 2/2] arm64: dts: rockchip: Add ALIENTEK QuarkPi-CA2
Date: Sun, 11 Oct 2026 11:31:42 +0800 [thread overview]
Message-ID: <9a8c6a76-8972-4b1e-8384-842668621fce@rock-chips.com> (raw)
In-Reply-To: <20261007-quarkpi-ca2-v8-2-b83192bed07b@163.com>
Hi Bob
在 2026/10/07 星期三 13:18, Bob Hui 写道:
> Add a device tree for the ALIENTEK QuarkPi-CA2, an RK3588S based card
> computer. The board comes in 4, 8 and 16 GiB LPDDR4X variants with
> 32 GB, 64 GB or 128 GB of eMMC; this was tested on the 16 GiB/128 GB
> one.
>
...
> +
> + vcc3v3_pcie: regulator-vcc3v3-pcie {
> + compatible = "regulator-fixed";
> + regulator-name = "vcc3v3_pcie";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + vin-supply = <&vcc12v_dcin>;
> + };
> +};
Is there any reason that you marked it as always-on?
next prev parent reply other threads:[~2026-10-11 3:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 5:18 [PATCH v8 0/2] " Bob Hui
2026-10-07 5:18 ` [PATCH v8 1/2] dt-bindings: arm: " Bob Hui
2026-10-07 9:52 ` Conor Dooley
2026-10-07 5:18 ` [PATCH v8 2/2] arm64: dts: " Bob Hui
[not found] ` <sashiko-outbox-162642@kernel.org>
2026-10-07 6:24 ` Bob Hui
2026-10-11 3:31 ` Shawn Lin [this message]
2026-10-12 20:00 ` Bob Hui
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=9a8c6a76-8972-4b1e-8384-842668621fce@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=andrew@lunn.ch \
--cc=bg9oxa@163.com \
--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 \
--cc=sashiko-bot@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®