devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Geyer <harald@ccbib.org>
To: Chen-Yu Tsai <wens@csie.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>
Cc: linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org,
	Torsten Duwe <duwe@suse.de>, Harald Geyer <harald@ccbib.org>
Subject: [PATCHv2] arm64: dts: allwinner: teres-i: Add GPIO port regulators
Date: Sat, 30 Apr 2022 19:10:09 +0000	[thread overview]
Message-ID: <20220430191009.73946-1-harald@ccbib.org> (raw)

Allwinner A64 SoC has separate supplies for PC, PD, PE, PG and PL.

Signed-off-by: Harald Geyer <harald@ccbib.org>
---
Changes since v1:
 * Add supplies for PD and PE even though they are matched from
   'regulator-name' properties, as this is a Linuxism.
 * Add generic IO voltage as supply for PF as this is an implicit
   (chip internal) dependency.

 arch/arm64/boot/dts/allwinner/sun50i-a64-teres-i.dts | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-teres-i.dts b/arch/arm64/boot/dts/allwinner/sun50i-a64-teres-i.dts
index aff0660b899c..1128030e4c25 100644
--- a/arch/arm64/boot/dts/allwinner/sun50i-a64-teres-i.dts
+++ b/arch/arm64/boot/dts/allwinner/sun50i-a64-teres-i.dts
@@ -197,6 +197,14 @@ &ohci1 {
 	status = "okay";
 };
 
+&pio {
+	vcc-pc-supply = <&reg_dcdc1>;
+	vcc-pd-supply = <&reg_dldo2>;
+	vcc-pe-supply = <&reg_aldo1>;
+	vcc-pf-supply = <&reg_dcdc1>;  /* No dedicated supply-pin for this */
+	vcc-pg-supply = <&reg_aldo2>;
+};
+
 &pwm {
 	status = "okay";
 };
-- 
2.35.2


             reply	other threads:[~2022-04-30 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30 19:10 Harald Geyer [this message]
2022-05-03  2:01 ` [PATCHv2] arm64: dts: allwinner: teres-i: Add GPIO port regulators Samuel Holland
2022-05-03 17:04   ` Jernej Škrabec

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=20220430191009.73946-1-harald@ccbib.org \
    --to=harald@ccbib.org \
    --cc=devicetree@vger.kernel.org \
    --cc=duwe@suse.de \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).