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.

<strong>Advanced</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Power</strong> <strong>Interface</strong> <strong>Specification</strong><br />

Arguments: (4)<br />

Arg0 – UUID (Buffer): 0811B06E-4A27-44F9-8D60-3CBBC22E7B48<br />

Arg1 – Revision ID (Integer): 1<br />

Arg2 – Count of Entries in Arg3 (Integer): 2<br />

Arg3 – DWORD capabilities (Buffer): First DWORD: as described in Section 6.2.11, Second<br />

DWORD: See Table 6-176<br />

Table 6-176 Platform-Wide _OSC Capabilities DWORD 2<br />

Bits Field Name Definition<br />

0 Processor Aggregator<br />

Device Support<br />

1 _PPC _OST Processing<br />

Support<br />

This bit is set if OSPM supports the Processor Aggregator device as<br />

described in Section 8.5, “Processor Aggregator Device”<br />

This bit is set if OSPM will evaluate the _OST object defined under a<br />

processor as a result of _PPC change notification (Notify 0x80)<br />

2 _PR3 Support This bit is set if OSPM supports reading _PR3<strong>and</strong> using power<br />

resources to switch power. Note this h<strong>and</strong>shake translates to an<br />

operating model that the platform <strong>and</strong> OSPM supports both the power<br />

model containing both D3hot <strong>and</strong> D3.<br />

3 Insertion / Ejection _OST<br />

Processing Support<br />

This bit is set if OSPM will evaluate the _OST object defined under a<br />

device when processing insertion <strong>and</strong> ejection source event codes.<br />

4 APEI Support This bit is set if OSPM supports the ACPI Platform Error <strong>Interface</strong>s.<br />

See Section 18, “ACPI Platform Error <strong>Interface</strong>s”.<br />

5 CPPC Support This bit is set if OSPM supports controlling processor performance via<br />

the interfaces described in the _CPC object.<br />

6 CPPC 2 Support This bit is set if OSPM supports revision 2 of the _CPC object.<br />

7 Platform Coordinated Low<br />

<strong>Power</strong> Idle Support<br />

8 OS Initiated Low <strong>Power</strong><br />

Idle Support<br />

9 Fast Thermal Sampling<br />

support<br />

10 Greater Than 16 p-state<br />

support<br />

This bit is set if OSPM supports platform coordinated low power idle<br />

states.*(see note, below)<br />

This bit is set if OSPM supports OS initiated low power idle states.<br />

*(see note, below)<br />

This bit is set if OSPM supports _TFP.<br />

31:11 Reserved (must be 0)<br />

This bit is set if OSPM supports greater than 16 p-states. If clear, no<br />

more than 16 p-states are supported.<br />

Note: * As part of the h<strong>and</strong>shake provided through _OSC the OS will pass in flags to indicate whether it<br />

supports Platform Coordinated Low <strong>Power</strong> Idle or OS Initiated Low <strong>Power</strong> Idle or both (see “Idle<br />

State Coordination”, Section 8.4.4.2), through flags 7 <strong>and</strong> 8. The platform will indicate which of the<br />

modes it supports in its response by clearing flags that are not supported. If both are supported,<br />

the default is platform coordinated <strong>and</strong> OSPM can switch the platform to OS Initiated via a<br />

processor architecture specific mechanism. By setting either flag 7 or 8 or both, the OSPM is<br />

asserting it supports any objects associated with Low <strong>Power</strong> Idle states (see LPI in<br />

316 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!