From: Maxime Ripard <maxime.ripard@bootlin.com>
To: "Clément Péron" <peron.clem@gmail.com>
Cc: devicetree@vger.kernel.org, linux-sunxi@googlegroups.com,
linux-kernel@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
Rob Herring <robh+dt@kernel.org>,
Jagan Teki <jagan@amarulasolutions.com>,
linux-arm-kernel@lists.infradead.org,
Icenowy Zheng <icenowy@aosc.io>
Subject: Re: [PATCH v2 1/5] arm64: allwinner: h6: orangepi: Add PIO regulators
Date: Fri, 5 Apr 2019 17:08:46 +0200 [thread overview]
Message-ID: <20190405150846.nurg6h4ykwtiib2v@flea> (raw)
In-Reply-To: <20190405122446.2101-1-peron.clem@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1216 bytes --]
On Fri, Apr 05, 2019 at 02:24:42PM +0200, Clément Péron wrote:
> OrangePi One Plus and OrangePi Lite2 use the same PIO regulators.
>
> Add this in the common device tree.
>
> Signed-off-by: Clément Péron <peron.clem@gmail.com>
> ---
> arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
> index b2526dac2fcf..fd2af5095425 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
> +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
> @@ -72,6 +72,12 @@
> status = "okay";
> };
>
> +&pio {
> + vcc-pc-supply = <®_bldo2>;
> + vcc-pd-supply = <®_cldo1>;
> + vcc-pg-supply = <®_bldo3>;
> +};
> +
> &r_i2c {
> status = "okay";
>
> @@ -191,6 +197,11 @@
> };
> };
>
> +&r_pio {
> + vcc-pl-supply = <®_aldo1>;
> + vcc-pm-supply = <®_bldo3>;
> +};
> +
How was this tested?
Please run checkpatch on your patches as well.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-05 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 12:24 [PATCH v2 1/5] arm64: allwinner: h6: orangepi: Add PIO regulators Clément Péron
2019-04-05 12:24 ` [PATCH v2 2/5] arm64: dts: allwinner: h6: pine64: " Clément Péron
2019-04-05 12:24 ` [PATCH v2 3/5] arm64: dts: allwinner: h6: move MMC pinctrl to dtsi Clément Péron
2019-04-05 12:24 ` [PATCH v2 4/5] dt-bindings: vendor-prefixes: add AZW Clément Péron
2019-04-05 12:42 ` Robin Murphy
2019-04-05 12:24 ` [PATCH v2 5/5] ARM: dts: sun50i: h6: Introduce Beelink GS1 board Clément Péron
2019-04-05 12:53 ` Clément Péron
2019-04-05 13:07 ` Clément Péron
2019-04-05 15:11 ` Maxime Ripard
2019-04-05 16:40 ` Clément Péron
2019-04-05 15:10 ` Maxime Ripard
2019-04-05 15:08 ` Maxime Ripard [this message]
2019-04-05 16:42 ` [PATCH v2 1/5] arm64: allwinner: h6: orangepi: Add PIO regulators Clément Péron
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=20190405150846.nurg6h4ykwtiib2v@flea \
--to=maxime.ripard@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=peron.clem@gmail.com \
--cc=robh+dt@kernel.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