linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Marek Vasut <marex@denx.de>, <linux-arm-kernel@lists.infradead.org>
Cc: <linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] ARM: dts: stm32: Move DHCOR BUCK3 VDD 2V9 adjustment to 1V8 DTSI
Date: Mon, 13 Jun 2022 09:42:41 +0200	[thread overview]
Message-ID: <0a86b3bc-7a7a-a66f-0d9f-85035aaff032@foss.st.com> (raw)
In-Reply-To: <20220504124945.77331-1-marex@denx.de>

Hi Marek

On 5/4/22 14:49, Marek Vasut wrote:
> The Buck3 on DHCOR is used to supply IO voltage. It can output either 3V3
> in the default DHCOR configuration, or 2V9 in case of AV96 DHCOR variant
> which has extra Empirion DCDC converter in front of the 1V8 IO supply, or
> outright 1V8 in case of 1V8 IO DHCOR without the Empirion DCDC converter.
> 
> The 2V9 mode in case of AV96 DHCOR variant is used to reduce unnecessarily
> high input voltage to the Empirion DCDC converter, so move it into matching
> DTSI to stop confusing users.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: linux-stm32@st-md-mailman.stormreply.com
> To: linux-arm-kernel@lists.infradead.org
> ---
>   arch/arm/boot/dts/stm32mp15xx-dhcor-io1v8.dtsi | 5 +++++
>   arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi   | 4 ++--
>   2 files changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcor-io1v8.dtsi b/arch/arm/boot/dts/stm32mp15xx-dhcor-io1v8.dtsi
> index 75172314d7afd..9937b28548c23 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dhcor-io1v8.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dhcor-io1v8.dtsi
> @@ -18,6 +18,11 @@ vdd_io: regulator-buck-io {
>   	};
>   };
>   
> +&vdd {
> +	regulator-min-microvolt = <2900000>;
> +	regulator-max-microvolt = <2900000>;
> +};
> +
>   &pwr_regulators {
>   	vdd-supply = <&vdd_io>;
>   };
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi b/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> index 6336c3ca0f0e2..134a798ad3f23 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dhcor-som.dtsi
> @@ -119,8 +119,8 @@ vdd_ddr: buck2 {
>   
>   			vdd: buck3 {
>   				regulator-name = "vdd";
> -				regulator-min-microvolt = <2900000>;
> -				regulator-max-microvolt = <2900000>;
> +				regulator-min-microvolt = <3300000>;
> +				regulator-max-microvolt = <3300000>;
>   				regulator-always-on;
>   				regulator-initial-mode = <0>;
>   				regulator-over-current-protection;

Applied on stm32-next.

Thanks.
Alex

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-06-13  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 12:49 [PATCH] ARM: dts: stm32: Move DHCOR BUCK3 VDD 2V9 adjustment to 1V8 DTSI Marek Vasut
2022-06-13  7:42 ` Alexandre TORGUE [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=0a86b3bc-7a7a-a66f-0d9f-85035aaff032@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=marex@denx.de \
    /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).