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 />

8.4 Declaring Processors<br />

Each processor in the system must be declared in the ACPI namespace in the \_SB scope.<br />

Declaration of processors in the \_PR scope was only required for platforms desiring compatibility<br />

with ACPI 1.0-based OSPM implementations. It is deprecated for all other uses. Processors are<br />

declared via the ASL Device statement. Declarations via the ASL Processor statement are<br />

deprecated. A Device definition for a processor is declared using the ACPI0007 hardware identifier<br />

(HID). Processor configuration information is provided exclusively by objects in the processor<br />

device's object list.<br />

When the platform uses the APIC interrupt model, UID object values under a processor device are<br />

used to associate processor devices with entries in the MADT.<br />

Processor-specific objects may be declared within the processor device's scope. These objects serve<br />

multiple purposes including processor performance state control. Other ACPI-defined device-related<br />

objects are also allowed under the processor device's scope (for example, the unique identifier object<br />

_UID mentioned above).<br />

With device-like characteristics attributed to processors, it is implied that a processor device driver<br />

will be loaded by OSPM to, at a minimum, process device notifications. OSPM will enumerate<br />

processors in the system using the ACPI Namespace, processor-specific native identification<br />

instructions, <strong>and</strong> the _HID method.<br />

For more information on the declaration of the processor device object, see Section 19.6.30, "Device<br />

(Declare Device Package)." Processor-specific child objects are described in the following sections.<br />

ACPI 6.0 introduces the notion of processor containers. Processor containers are declared using the<br />

Processor Container Device. A processor container can be used to describe a collection of<br />

associated processors that share common resources, such as shared caches, <strong>and</strong> which have power<br />

states that affect the processors in the collection. For more information see Section 8.4.3.1<br />

"Processor Container Device”.<br />

8.4.1 _PDC (Processor Driver Capabilities)<br />

This optional object is a method that is used by OSPM to communicate to the platform the level of<br />

processor power management support provided by OSPM. This object is a child object of the<br />

processor. OSPM evaluates _PDC prior to evaluating any other processor power management<br />

objects returning configuration information.<br />

The _PDC object provides OSPM a mechanism to convey to the platform the capabilities supported<br />

by OSPM for processor power management. This allows the platform to modify the ACPI<br />

namespace objects returning configuration information for processor power management based on<br />

the level of support provided by OSPM. Using this method provides a mechanism for OEMs to<br />

provide support for new technologies on legacy OSes, while also allowing OSPM to leverage new<br />

technologies on platforms capable of supporting them. This method is evaluated once during<br />

processor device initialization, <strong>and</strong> will not be re-evaluated during resume from a sleep state<br />

transition. The platform must preserve state information across S1-S3 sleep state transitions.<br />

Arguments: (1)<br />

Arg0 – A variable-length Buffer containing a list of capabilities as described below<br />

Version 6.0 427

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

Saved successfully!

Ooh no, something went wrong!