CONFIG_CAF_FORCE_POWER_DOWN_EVENTS

Enable force Power down event

Type: bool

Help

Enable power manager event to put the device into power down mode when processed.
It means the power down would be processed without the delay that is
normally applied inside power manager.
The event would be send only if the power manager is in IDLE state.
The power down event would be send ignoring the fact if any of the modules
requires ACTIVE state.
The reasult of such situation would be powering down the device to SUSPENDED state.
To avoid this the user is responsible in clearing all power ACTIVE requirements
before sending this event.
The event is here to support very specyfic requirement when the device
has to limit is power usage no matter what.
The possible usage scenarios are:
- Reaction to USB SUSPEND on bus powered device
- Reaction to power loss if we have for example to disable LEDs to keep power
  to do some important jobs before we lost all the power stored in system.

Direct dependencies

CAF

(Includes any dependencies from ifs and menus.)

Defaults

No defaults. Implicitly defaults to n.

Kconfig definition

At <nRF>/subsys/caf/events/Kconfig.force_power_down_event:7

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:33<Zephyr>/modules/Kconfig:6<nRF>/doc/_build/kconfig/Kconfig.modules:2<nRF>/Kconfig.nrf:81<nRF>/subsys/Kconfig:50<nRF>/subsys/caf/Kconfig:15<nRF>/subsys/caf/events/Kconfig:146

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Common Application Framework → Event options

config CAF_FORCE_POWER_DOWN_EVENTS
    bool "Enable force Power down event"
    depends on CAF
    help
      Enable power manager event to put the device into power down mode when processed.
      It means the power down would be processed without the delay that is
      normally applied inside power manager.
      The event would be send only if the power manager is in IDLE state.
      The power down event would be send ignoring the fact if any of the modules
      requires ACTIVE state.
      The reasult of such situation would be powering down the device to SUSPENDED state.
      To avoid this the user is responsible in clearing all power ACTIVE requirements
      before sending this event.
      The event is here to support very specyfic requirement when the device
      has to limit is power usage no matter what.
      The possible usage scenarios are:
      - Reaction to USB SUSPEND on bus powered device
      - Reaction to power loss if we have for example to disable LEDs to keep power
        to do some important jobs before we lost all the power stored in system.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)