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.

Device <strong>Configuration</strong><br />

Method(_EJ0, 1) { // Remove all power to device}<br />

}<br />

Device (S2F7) {<br />

// Slot 2, Func#7 on bus P2P2<br />

Name(_ADR,0x00030007)<br />

Method(_EJ0, 1) { // Remove all power to device}<br />

}<br />

} // end P2P2<br />

} // end PCI0<br />

} // end Scope (\_SB)<br />

OSPM will configure a PCI device on a card hot-plugged into slot 1 or slot 2, with a cache line size<br />

of 32 (Notice this field is in DWORDs), latency timer of 64, enable SERR, but leave PERR alone.<br />

6.2.9 _HPX (Hot Plug Parameter Extensions)<br />

This optional object provides platform-specific information to the OSPM PCI driver component<br />

responsible for configuring hot-add PCI, PCI-X, or PCI Express devices. The information conveyed<br />

applies to the entire hierarchy downward from the scope containing the _HPX object. If another<br />

_HPX object is encountered downstream, the settings conveyed by the lower-level object apply to<br />

that scope downward.<br />

OSPM uses the information returned by _HPX to determine how to configure PCI devices that are<br />

hot-plugged into the system, <strong>and</strong> to configure devices not configured by the platform firmware<br />

during initial system boot. The _HPX object is placed within the scope of a PCI-compatible bus (see<br />

the second Note below for restrictions) where this behavior is desired, such as a bus with hot-plug<br />

slots. It returns a single package that contains one or more sub-packages, each containing a single<br />

Setting Record. Each such Setting Record contains a Setting Type (INTEGER), a Revision number<br />

(INTEGER) <strong>and</strong> type/revision specific contents.<br />

The format of data returned by the _HPX object is extensible. The Setting Type <strong>and</strong> Revision<br />

number determine the format of the Setting Record. OSPM ignores Setting Records of types that it<br />

does not underst<strong>and</strong>. A Setting Record with higher Revision number supersedes that with lower<br />

revision number, however, the _HPX method can return both together, OSPM shall use the one with<br />

highest revision number that it underst<strong>and</strong>s.<br />

_HPX may return multiple types or Record Settings (each setting in a single sub-package.) OSPM is<br />

responsible for detecting the type of hot plugged device <strong>and</strong> for applying the appropriate settings.<br />

OSPM is also responsible for detecting the device / port type of the PCI Express device <strong>and</strong> applying<br />

the appropriate settings provided. For example, the Secondary Uncorrectable Error Severity <strong>and</strong><br />

Secondary Uncorrectable Error Mask settings of Type 2 record are only applicable to PCI Express to<br />

PCI-X/PCI Bridge whose device / port type is 1000b. Similarly, AER settings are only applicable to<br />

hot plug PCI Express devices that support the optional AER capability.<br />

Arguments:<br />

None<br />

Return Value:<br />

A variable-length Package containing a list of Packages, each containing a single PCI or PCI-X<br />

Record Setting as described below<br />

The _HPX object supersedes the _HPP object. If the _HPP <strong>and</strong> _HPX objects exist within a device’s<br />

scope, OSPM will only evaluate the _HPX object.<br />

Version 6.0 307

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

Saved successfully!

Ooh no, something went wrong!