Power off without PMIC

[Dat Tran]

Hi, we make custom board base on STM32MP15 and without PMIC and have problem with power off command.

Does anyone know any document or hint about this? All research we have found always include PMIC.

 

 

[PatrickF]

Hi @Dat Tran ,

Could you details which HW have you provisioned on your board to power off the supplies ? Is it controlled using I2C or GPIO or else ? I think OpTee need to be adapted to your HW control.

Regards.

[Dat Tran]

Hi Patrick, we don't use any special hw to power off the supplies. We use two LTC3406B to generate 1.215V for VDD_CORE and 1.35V for VDD_DDR, and we follow document below to make custom board. 

And we are using buildroot.

I thought there are some registers we set to enter STOP or standby mode, similar to F4, F7 or H7. 

Do you know where those code are on STM32MP1?

 

 

 

[PatrickF]

Hi,

maybe have a look to:

• https://wiki.st.com/stm32mpu/wiki/Power_overview
• https://wiki.st.com/stm32mpu/wiki/How_to_define_your_low-power_strategy#On_STM32MP15x_lines
• AN5256.pdf - STM32MP151, STM32MP153 and STM32MP157 discrete power supply hardware integration
• AN5109.pdf - STM32MP15x lines using low-power modes 

'Power OFF' is different than Standby. Power OFF is not really a low power mode.
Power OFF need specific HW to shutdown all supplies under SW control whereas Standby deactivate PWR_ON pin to shutdown all supplies except VDD with external HW (usually Enable of discrete regulators), allowing wakeup by WKUP pins (or internal sources like TAMP or RTC).

Power control SW is inside OpTee, but unless specifc power mechanism and HW does not need to be modified (only device tree adaptations).

 

Regards.

[Dat Tran]

Thank PatrickF,

So power off command won't work without PMIC or special HW.

But does "echo mem > /sys/power/state" still work? 

When we send that command, power consumption goes lower but not too much, so we want to see where the issue is. At the low layer, does this command will set some registers to enter low power mode?

 

 

 

 

[PatrickF]

Hi,

note in https://wiki.st.com/stm32mpu/wiki/Power_overview#API_description
"The whole system activity is stopped and a low-power mode is entered. The software selects the deepest mode according to the activated wakeup source(s)."

In other words, to go to Standby with DDR OFF (the lowest one possible with your HW if you are using PWR_ON to shutdown VDDCORE and DDR supplies), only WKUP pins should be enabled.
If PWR_ON is not toggling, you should look at SW messages/traces to know who avoid this. https://wiki.st.com/stm32mpu/wiki/Power_overview#How_to_trace_and_debug

Regards.

[Dat Tran]

Thank PatricF,

If I use PWR_ON to shutdown VDD_CORE and DDR, then RTC wakeup won't work? because you said "only WKUP pins should be enabled". 

Another question is, if everything is setup correctly, when I type the command 

echo mem > /sys/power/state

then I should see PWR_ON from high to low?

 

 

[PatrickF]

Hi,

sorry, I was not precise enough. Yes, in addition to WUP pins, RTC (regular or alarm) and TAMP (tamper detection) and reset could wakeup from STANBDY.
This is listed in Reference Manual (abstract below):

Regarding "echo mem > /sys/power/state", I'm not SW expert, but my understanding is that lowest achieved low power mode depend on enabled wake up sources in Linux. Details are available in wiki and application notes.

I don't know if you are hobbyist or working within a team, but having made the choice not to implement STPMIC1 assume you anticipated potential limitations in low power modes flexibility and additional customization on your side as all HW and SW examples with ST development boards are build around STPMIC1.

Regards.