27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

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.

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

Device(GPE5) {<br />

Name(_HID, “ACPI0006”)<br />

}<br />

Method(_L02) { … }<br />

Method(_E07) { … }<br />

Method(_W04) { … }<br />

9.11 Module Device<br />

This optional device is a container object that acts as a bus node in a namespace. It may contain child<br />

objects that are devices or buses. The module device is declared using the ACPI0004 hardware<br />

identifier (HID).<br />

If the module device contains a _CRS object, the “bus” described by this object is assumed to have<br />

these resources available for consumption by its child devices. If a _CRS object is present, any<br />

resources not produced in the module device’s _CRS object may not be allocated to child devices.<br />

Providing a _CRS object is undesirable in some module devices. For example, consider a module<br />

device used to describe an add-in board containing multiple host bridges without any shared<br />

resource decoding logic. In this case the resource ranges available to the host bridges are not<br />

controlled by any entity residing on the add-in board, implying that a _CRS object in the associated<br />

module device would not describe any real feature of the underlying hardware. A module device<br />

must contain a _CRS object if the device contains any PCI host bridge devices.<br />

To account for cases like this, the system designer may optionally omit the module device’s _CRS<br />

object. If no _CRS object is present, OSPM will assume that the module device is a simple container<br />

object that does not produce the resources consumed by its child devices. In this case, OSPM will<br />

assign resources to the child devices as if they were direct children of the module device's parent<br />

object.<br />

For an example with a module device _CRS object present, consider a Module Device containing<br />

three child memory devices. If the _CRS object for the Module Device contains memory from 2 GB<br />

through 6 GB, then the child memory devices may only be assigned addresses within this range.<br />

518 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!