From: Samuel Holland <samuel@sholland.org>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] arm64: dts: allwinner: h6: Enable CPU opp tables for OrangePi One Plus
Date: Tue, 5 Jul 2022 00:17:34 -0500 [thread overview]
Message-ID: <93bbf82c-5868-e5ad-6325-7c4e6ba50907@sholland.org> (raw)
In-Reply-To: <20220510153006.279233-2-amadeus@jmu.edu.cn>
On 5/10/22 10:30 AM, Chukun Pan wrote:
> Enable CPU opp tables for OrangePi One Plus.
>
> This needs to change the CPU regulator max voltage to fit
> the OPP table.
>
> Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> ---
> arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
> index 92745128fcfe..7773c51438ce 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
> +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
Putting the changes in this file also applies them to the OrangePi Lite2 and
OrangePi 3.
Did you test OrangePi Lite2? They both use the same PMIC with a similar
configuration, so it may be safe to assume that what works on OrangePi One Plus
also works there, but I am not sure.
OrangePi 3 already includes the OPP header and these changes, so it is safe but
redundant.
Either these changes need to be made in sun50i-h6-orangepi-one-plus.dts, or we
need to remove the duplicate changes from sun50i-h6-orangepi-3.dts.
Regards,
Samuel
> @@ -5,6 +5,7 @@
> /dts-v1/;
>
> #include "sun50i-h6.dtsi"
> +#include "sun50i-h6-cpu-opp.dtsi"
>
> #include <dt-bindings/gpio/gpio.h>
>
> @@ -64,6 +65,10 @@ reg_vcc5v: vcc5v {
> };
> };
>
> +&cpu0 {
> + cpu-supply = <®_dcdca>;
> +};
> +
> &de {
> status = "okay";
> };
> @@ -208,7 +213,7 @@ reg_cldo3: cldo3 {
> reg_dcdca: dcdca {
> regulator-always-on;
> regulator-min-microvolt = <810000>;
> - regulator-max-microvolt = <1080000>;
> + regulator-max-microvolt = <1160000>;
> regulator-name = "vdd-cpu";
> };
>
>
prev parent reply other threads:[~2022-07-05 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 15:30 [PATCH v2 0/1] " Chukun Pan
2022-05-10 15:30 ` [PATCH v2 1/1] " Chukun Pan
2022-07-05 5:17 ` Samuel Holland [this message]
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=93bbf82c-5868-e5ad-6325-7c4e6ba50907@sholland.org \
--to=samuel@sholland.org \
--cc=amadeus@jmu.edu.cn \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--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
all inboxes | Powered by JetHome®