09.12.2012 Views

Cortex-A8 Technical Reference Manual - ARM Information Center

Cortex-A8 Technical Reference Manual - ARM Information Center

Cortex-A8 Technical Reference Manual - ARM Information Center

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10.3 Power control<br />

10.3.1 Dynamic power management<br />

Clock, Reset, and Power Control<br />

Both the clocks and resets in the processor play key roles in the power management of the<br />

processor, enabling islands to be powered down or powered up in a controlled manner. They<br />

also provide many key control mechanisms to manage dynamic power.<br />

This section describes:<br />

• Dynamic power management<br />

• Static or leakage power management on page 10-11<br />

• Debugging the processor while powered down on page 10-18<br />

• L1 data and L2 cache power domains on page 10-19<br />

• Special note on reset during power transition on page 10-22.<br />

The processor has many different dynamic power management facilities. The most common<br />

form of dynamic power management is control of the clock network within the processor.<br />

The processor has three levels of clock gating to manage dynamic power. The levels correspond<br />

to the following functions:<br />

Level 1 This is architectural gating, also known as Wait-For-Interrupt (WFI), or the<br />

CLKSTOPREQ and CLKSTOPACK signals on the <strong>Cortex</strong>-<strong>A8</strong> processor.<br />

Level 2 This is major function gating, such as NEON, ETM, or integer core gating.<br />

Level 3 This is state element gating, such as local clock gating.<br />

The processor contains all hardware necessary for architecture, unit, and local clock gating. No<br />

external hardware is required to clock gate the processor.<br />

Wait-For-Interrupt architecture<br />

Executing a Wait-For-Interrupt instruction puts the processor into a low-power state until one<br />

of the following occurs:<br />

• an IRQ or FIQ interrupt<br />

• a halting debug event when the DBGNOCLKSTOP signal is HIGH.<br />

See Halting debug event on page 12-51 for information on halting debug events.<br />

Note<br />

• If you are debugging software running on the <strong>Cortex</strong>-<strong>A8</strong> processor, DBGNOCLKSTOP<br />

must be HIGH. Otherwise, halting debug events do not work as architected and the APB<br />

interface does not return a response when accessing the ETM, CTI, or core domain debug<br />

registers. See Table 12-3 on page 12-6 for information on the debug registers that are in<br />

the core.<br />

• If DBGNOCLKSTOP is HIGH and you execute the Wait-For-Interrupt instruction, the<br />

processor goes into an idle state but not into a low-power state.<br />

• The STANDBYWFI pin remains HIGH even when DBGNOCLKSTOP is HIGH.<br />

When executing the WFI instruction, the processor waits for the following events to complete<br />

before entering the idle or low-power state:<br />

• L1 data memory system loads and stores are complete<br />

• all L1 instruction memory system fetches are complete<br />

<strong>ARM</strong> DDI 0344K Copyright © 2006-2010 <strong>ARM</strong> Limited. All rights reserved. 10-8<br />

ID060510 Non-Confidential

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!