diff options
| author | Ahmad Fatoum <a.fatoum@pengutronix.de> | 2022-06-02 06:28:31 +0200 |
|---|---|---|
| committer | Ahmad Fatoum <a.fatoum@pengutronix.de> | 2022-06-02 06:47:20 +0200 |
| commit | 9eed71b7221c5fc7ed887f1087e42c9f1a62f581 (patch) | |
| tree | 83b0ef358dd723470d531f3a4886f11b2b68a85d /fdts/stm32mp15xx-osd32.dtsi | |
| parent | 35f4c7295bafeb32c8bcbdfb6a3f2e74a57e732b (diff) | |
| download | arm-trusted-firmware-9eed71b7221c5fc7ed887f1087e42c9f1a62f581.tar.gz | |
fix(stm32mp1): fdts: stm32mp1: align DDR regulators with new driver
With recent changes, TF-A now panics on MC-1, Avenger96 and Odyssey:
NOTICE: CPU: STM32MP157C?? Rev.B
NOTICE: Model: Linux Automation MC-1 board
ERROR: regul ldo3: max value 750 is invalid
PANIC at PC : 0x2ffeebb7
as the driver takes great offense at the content of the device
tree. The parts in question were copy-pasted from ST DTs, but
those ST DTs were fixed by commit 67d95409baae
("refactor(stm32mp1-fdts): update regulator description").
Fix the breakage by transplanting the same changes into all
remaining STM32MP1 DTs.
Change was boot-tested on MC-1, but only build tested for the
other two.
Fixes: bba9fdee589f ("feat(stm32mp1): add regulator framework compilation")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Change-Id: I143d0091625f62c313b3b71449c9ad99583d01c8
Diffstat (limited to 'fdts/stm32mp15xx-osd32.dtsi')
| -rw-r--r-- | fdts/stm32mp15xx-osd32.dtsi | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/fdts/stm32mp15xx-osd32.dtsi b/fdts/stm32mp15xx-osd32.dtsi index 76a25613a..ca6723562 100644 --- a/fdts/stm32mp15xx-osd32.dtsi +++ b/fdts/stm32mp15xx-osd32.dtsi @@ -81,10 +81,9 @@ vtt_ddr: ldo3 { regulator-name = "vtt_ddr"; - regulator-min-microvolt = <500000>; - regulator-max-microvolt = <750000>; regulator-always-on; regulator-over-current-protection; + st,regulator-sink-source; }; vdd_usb: ldo4 { @@ -110,7 +109,6 @@ vref_ddr: vref_ddr { regulator-name = "vref_ddr"; regulator-always-on; - regulator-over-current-protection; }; bst_out: boost { |