public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH V3 12/14] ARM: dts: stm32: Repair PMIC configuration on AV96
Date: Wed, 1 Apr 2020 13:06:27 +0200	[thread overview]
Message-ID: <7920cb9f-ab01-2a67-83ef-d65119dafff8@denx.de> (raw)
In-Reply-To: <845efdc0f66841e98c2af649c36203fd@SFHDAG6NODE3.st.com>

On 4/1/20 9:34 AM, Patrick DELAUNAY wrote:
> Hi Marek and Pascal,

Hi,

[...]

>> @@ -167,7 +178,7 @@
>>
>>  			vddcore: buck1 {
>>  				regulator-name = "vddcore";
>> -				regulator-min-microvolt = <1200000>;
>> +				regulator-min-microvolt = <800000>;
> 
> I don't understood this modification, If I correctly remember, on STM32MP15x 
> On ST boards, we set this value to 1200000 to protect VDDCORE on
> SOC (it is not allowed to be reduce lower than 1,2V.
> 
> 0.8V is the minimal supported voltage by STPMIC but not the minal expected 
> VDDCORE.

Then we should likely drop this part.

That said, is the core voltage supposed to be 1V2 even in sleep states ?

>> @@ -185,8 +196,8 @@
>>
>>  			vdd: buck3 {
>>  				regulator-name = "vdd";
>> -				regulator-min-microvolt = <3300000>;
>> -				regulator-max-microvolt = <3300000>;
>> +				regulator-min-microvolt = <2900000>;
>> +				regulator-max-microvolt = <2900000>;
>>  				regulator-always-on;
>>  				st,mask_reset;
>>  				regulator-initial-mode = <0>;
>> @@ -268,6 +279,7 @@
>>  				regulator-name = "vbus_otg";
>>  				interrupts = <IT_OCP_OTG 0>;
>>  				interrupt-parent = <&pmic>;
>> +				regulator-active-discharge = <1>;
> 
> It seems this setting introduced other-consumption, it should not be used.

Other-consumption ? What does that mean ?

  reply	other threads:[~2020-04-01 11:06 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 17:51 [PATCH V3 00/14] ARM: stm32: Fix Avenger96 Marek Vasut
2020-03-31 17:51 ` [PATCH V3 01/14] ARM: dts: stm32: Repair SD1 pre-reloc pinmux DT node on AV96 Marek Vasut
2020-04-01  9:54   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 02/14] ARM: dts: stm32: Add alternate pinmux for SDMMC1 direction pins Marek Vasut
2020-04-01  9:55   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 03/14] ARM: dts: stm32: Repair SDMMC1 operation on AV96 Marek Vasut
2020-04-01  9:55   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 04/14] ARM: dts: stm32: Add alternate pinmux for SDMMC2 pins 4-7 Marek Vasut
2020-04-01  9:56   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 05/14] ARM: dts: stm32: Repair SDMMC2 operation Marek Vasut
2020-04-01  9:56   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 06/14] ARM: dts: stm32: Add QSPI NOR on AV96 Marek Vasut
2020-04-01  8:17   ` Patrick DELAUNAY
2020-04-01  9:59   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 07/14] ARM: dts: stm32: Use DT alias for the configuration EEPROM Marek Vasut
2020-04-01  9:59   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 08/14] ARM: dts: stm32: Add configuration EEPROM on AV96 Marek Vasut
2020-04-01 10:02   ` Patrick DELAUNAY
2020-04-01 11:00     ` Marek Vasut
2020-03-31 17:51 ` [PATCH V3 09/14] ARM: dts: stm32: Add alternate pinmux for ethernet RGMII Marek Vasut
2020-04-01 10:03   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 10/14] ARM: dts: stm32: Repair ethernet operation on AV96 Marek Vasut
2020-04-01 10:03   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 11/14] ARM: dts: stm32: Add missing ethernet PHY reset " Marek Vasut
2020-04-01 10:04   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 12/14] ARM: dts: stm32: Repair PMIC configuration " Marek Vasut
2020-04-01  7:34   ` Patrick DELAUNAY
2020-04-01 11:06     ` Marek Vasut [this message]
2020-04-01 12:45       ` Patrice CHOTARD
2020-04-01 12:53         ` Marek Vasut
2020-04-01 13:52           ` Patrick DELAUNAY
2020-04-01 13:53             ` Marek Vasut
2020-04-02 12:53             ` Pascal PAILLET-LME
2020-04-02 13:07               ` Marek Vasut
2020-04-02 13:43                 ` Pascal PAILLET-LME
2020-04-09 11:28                   ` Marek Vasut
2020-04-01 10:04   ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 13/14] ARM: dts: stm32: Adjust PLL4 settings " Marek Vasut
2020-04-01 10:24   ` Patrick DELAUNAY
2020-04-01 11:09     ` Marek Vasut
2020-04-01 16:49       ` Gerald BAEZA
2020-04-01 17:45         ` Manivannan Sadhasivam
2020-04-01 18:48         ` Marek Vasut
2020-04-02  7:44           ` Gerald BAEZA
2020-04-02 13:04             ` Marek Vasut
2020-04-24 14:31               ` Patrick DELAUNAY
2020-03-31 17:51 ` [PATCH V3 14/14] ARM: dts: stm32: Split AV96 into DHCOR SoM and AV96 board Marek Vasut
2020-04-24 14:31   ` Patrick DELAUNAY
2020-04-27 10:29     ` Marek Vasut
2020-04-27 14:00       ` Patrick DELAUNAY
2020-04-27 14:34         ` Marek Vasut

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=7920cb9f-ab01-2a67-83ef-d65119dafff8@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.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