power_manager
Overview
The power manager demo application demonstrates how to change power modes in the KSDK. The difference between this demo and power_mode_switch is, this demo uses a notification framework to inform application about the mode change. Application could register callback to the notification framework, when power mode changes, the callback function is called and user can do something, such as closing debug console before entering low power mode, and opening debug console after exiting low power mode.
When this demo runs, the power mode menu is shown in the debug console, where the user can set the MCU to a specific power mode. User can also set the wakeup source following the debug console prompts.
Tips: This demo is to show how the various power mode can switch to each other. However, in actual low power use case, to save energy and reduce the consumption even more, many things can be done including:
Disable the clock for unnecessary modules during low power mode. That means, programmer can disable the clocks before entering the low power mode and re-enable them after exiting the low power mode when necessary.
Disable the function for unnecessary part of a module when other part would keep working in low power mode. At the most time, more powerful function means more power consumption. For example, disable the digital function for the unnecessary pin mux, and so on.
Set the proper pin state (direction and logic level) according to the actual application hardware. Otherwise, there would be current leakage on the pin, which will increase the power consumption.
Other low power consideration based on the actual application hardware.