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

Note: For event numbers less than 255, _Exx <strong>and</strong> _Lxx methods may be used instead. In this case, they<br />

take precedence <strong>and</strong> _EVT will not be invoked.<br />

Example:<br />

Scope (\_SB.GPI2)<br />

{<br />

Method (_EVT,1) {<br />

// H<strong>and</strong>le all ACPI Events signaled by GPIO Controller GPI2<br />

Switch (Arg0)<br />

{<br />

Case (300) {<br />

…<br />

Notify (\_SB.DEVX, 0x80)<br />

}<br />

Case (1801) {<br />

…<br />

Notify (\_SB.DEVY, 0x80)<br />

}<br />

Case (14…) {<br />

…<br />

Notify (\_SB.DEVZ, 0x80)<br />

}<br />

…<br />

}<br />

} //End of Method<br />

} //End of Scope<br />

5.6.6 Device Object Notifications<br />

During normal operation, the platform needs to notify OSPM of various device-related events. These<br />

notifications are accomplished using the Notify operator, which indicates a target device, thermal<br />

zone, or processor object <strong>and</strong> a notification value that signifies the purpose of the notification.<br />

Notification values from 0 through 0x7F are common across all device object types. Notification<br />

values of 0xC0 <strong>and</strong> above are reserved for definition by hardware vendors for hardware specific<br />

notifications. Notification values from 0x80 to 0xBF are device-specific <strong>and</strong> defined by each such<br />

device. For more information on the Notify operator, see Section 19.6.92, “Notify (Notify).”<br />

Table 5-142 Device Object Notification Values<br />

Value Description<br />

0 Bus Check. This notification is performed on a device object to indicate to OSPM that it<br />

needs to perform a Plug <strong>and</strong> Play re-enumeration operation on the device tree starting from<br />

the point where it has been notified. OSPM will typically perform a full enumeration<br />

automatically at boot time, but after system initialization it is the responsibility of the ACPI<br />

AML code to notify OSPM whenever a re-enumeration operation is required. The more<br />

accurately <strong>and</strong> closer to the actual change in the device tree the notification can be done, the<br />

more efficient the operating system’s response will be; however, it can also be an issue<br />

when a device change cannot be confirmed. For example, if the hardware cannot recognize<br />

a device change for a particular location during a system sleeping state, it issues a Bus<br />

Check notification on wake to inform OSPM that it needs to check the configuration for a<br />

device change.<br />

250 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!