Can't enable 'HAS_PM' to support power management notification

[Ohad Gal]

Hello,

I'm trying to enable the Power management for nRF9161 over nRF-Connect SDK2.5

the prj.conf has an entry of 'CONFIG_PM=y'

but it not accepted because we do not satisty the condition "HAS_PM=y"

the condition 'CONFIG_SYS_CLOCK_EXISTS=y' is found inside the ".config" generated file so it is enabled.

however the second condition "HAS_PM=y" is not satisfied...

I couldn't find "where" to configure and "what" to configure, in order to have this feature "CONFIG_PM=y" enabled...

FYI, we also enabled:

CONFIG_PM_DEVICE=y

CONFIG_PM_DEVICE_RUNTIME=y

[Vidar Berg]

Hello,

Support for the PM subsystem have been removed for the nRF chips, as it is not needed (https://github.com/nrfconnect/sdk-zephyr/commit/96b38273138f05dd06cf7a58fa361f401e773e5e).  However, you can still use CONFIG_PM_DEVICE_RUNTIME if you need to suspend peripherals at runtime.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/nrf/test_and_optimize/optimizing/power.html 

Best regards,

Vidar

[Ohad Gal]

Hi,

that doesn't help much

what I realy need is to be notified going into IDLE and out of IDLE by the operating system.

we turn ON and OFF the main UART for the terminal

otherwise it is not possible to have the main clock closed (UART has baud rate 115200)

void power_state_enter_cb(enum pm_state state);

void power_state_exit_cb(enum pm_state state);

static struct pm_notifier power_state_notifier = {.state_entry = &power_state_enter_cb, .state_exit = &power_state_exit_cb};

 

main()

{

...

  pm_notifier_register(&power_state_notifier);

...

[Vidar Berg]

If you are using idle hooks to power the UARTE on and off, you will need to prevent the CPU from entering idle mode while the UART is receiving data. This approach does not seem very power-efficient.

[Ohad Gal]

Hi

Well, the firmware wakes up every 1 minute so we can postpone cpu idle while UART TX needs to finish (we can poll the register). In practice there is no much UART going on and typically no one looking at it. This firmware get a total of 2uA in the dev kit. Without this, it’s about 20uA more when I don’t stop the UARTE (I do stop the RX side based on an RTS signal)

 

So what is the chance to get the binaries of the PM back? If I add “select CONFIG_PM” it does compile but is missing some object files…)

[Vidar Berg]

I still don't understand why the UART can't just be suspended with the PM_DEVICE action after the transaction is complete. You could also have used the UART ASYNC API with the low power mode enabled (CONFIG_UART_0_NRF_ASYNC_LOW_POWER). There's also the Low power UART driver. It does not work with standard flow control signals, however.

Ohad Gal said:

So what is the chance to get the binaries of the PM back? If I add “select CONFIG_PM” it does compile but is missing some object files…)

You need to revert the changes introduced by the commit I linked to in my initial reply.