27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Processor <strong>Configuration</strong> <strong>and</strong> Control<br />

shallower power state in the parent is also enabled. Taking the system described in Figure 8-46, the<br />

states <strong>and</strong> EPS value for the states is described in the table below:<br />

Table 8-242 Enabled Parent State values for example system<br />

System Level Processor<br />

Container LPI States<br />

Enabled Parent State<br />

0 Running N/A<br />

1 <strong>Power</strong> Down 0<br />

Cluster Level Processor Container LPI States<br />

0 Running N/A<br />

1 Clock Gating 0 – System must be running if cluster is clock gated<br />

2 Retention 0 – System must be running if cluster is in retention<br />

3 <strong>Power</strong> Down 1 – System may be in power down if cluster is in power down<br />

Core Level Processor Container LPI States<br />

0 Running N/A<br />

1 Clock Gating 1 – Cluster may be clock gated or running of core is clock<br />

gated<br />

2 Retention 2 – Cluster may running, or clock gated, or in retention if core is<br />

in retention<br />

3 <strong>Power</strong> Down 3 – All states at cluster level are supported if the core is<br />

powered down<br />

8.4.4.3.3 <strong>Power</strong>, Minimum Residency, <strong>and</strong> Worst Case Wakeup Latency<br />

<strong>Power</strong> is not included in _LPI since relative power of different states (along with minimum<br />

residency to comprehend transition energy), <strong>and</strong> not absolute power, drive OSPM idle state<br />

decisions. To correctly convey relative power, local states in _LPI must be declared in power<br />

consumption order. That is, the local states for a particular hierarchy node must be listed from<br />

highest power (shallowest) to lowest power (deepest).<br />

The worst case wakeup latency (WCWL) for a particular local state is the longest time from when a<br />

wake interrupt is asserted, to when the hierarchy node can return to execution. Generally, the<br />

WCWL will be the idle state’s exit latency plus some portion of its entry latency. How much of the<br />

entry flow is included depends on where (<strong>and</strong> if) the platform supports checking for pending wake<br />

events <strong>and</strong> aborting the idle state entry. For any given power state there will be a “point of no return”<br />

after which the entry into the power state cannot be reversed. This is illustrated in Figure 8-47<br />

below. The WCWL must include the time period from the point of no return to the time at which a<br />

wake up interrupt can be h<strong>and</strong>led.<br />

Version 6.0 447

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

Saved successfully!

Ooh no, something went wrong!