SPRUI30H November 2015 – May 2024 DRA745 , DRA746 , DRA750 , DRA756
The user can configure the local power management through the STANDBY_CORE_SYSCONFIG, IDLE_CORE_SYSCONFIG, and WUGEN_IRQ_EN registers. The user can:
The IPUx subsystem provides three sleep modes:
During sleep mode, the system clock can be stopped, but the free-running clock input must still be running to allow the processor to be wakened by an interrupt or an event. The sleep modes are invoked by wait for interrupt (WFI) or wait for event (WFE) instructions. The processor clock is automatically stopped, waiting for an interrupt or an event. Deep-sleep mode also stops the processor clock, but this can also be supported by the PRCM module. A combined signal is generated from the two Cortex-M4 processors in deep-sleep mode to initiate another power state and let the PRCM module handle the next power states. At this time, software must ensure that all IPUx_UNICACHE background operations (for example, maintenance) are complete.
Table 7-4 describes local clock gating.
Cortex-M4 CPU Mode | IPUx_C1 On | IPUx_C1 Sleep | IPUx_C1 Deep Sleep |
---|---|---|---|
IPUx_C0 On | On | Functional clock 2 stopped locally | Functional clock 2 stopped locally |
IPUx_C0 Sleep | Functional clock 1 stopped locally | Functional clock 1 and clock 2 stopped locally | Functional clock 1 and clock 2 stopped locally |
IPUx_C0 Deep Sleep | Functional clock 1 stopped locally | Functional clock 1 and clock 2 stopped locally | Standby request to power-management module |
For information about source clock gating and for a description of the sleep/wake-up transitions, see Power, Reset, and Clock Management.