18.12.2012 Views

Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification

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.

Arguments:<br />

None<br />

Return Value:<br />

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

An Integer containing a device status bitmap:<br />

Bit 0 – Set if the device is present.<br />

Bit 1 – Set if the device is enabled <strong>and</strong> decoding its resources.<br />

Bit 2 – Set if the device should be shown in the UI.<br />

Bit 3 – Set if the device is functioning properly (cleared if device failed its diagnostics).<br />

Bit 4 – Set if the battery is present.<br />

Bits 5–31 – Reserved (must be cleared).<br />

Return Value Information<br />

If bit 0 is cleared, then bit 1 must also be cleared (in other words, a device that is not present cannot<br />

be enabled).<br />

A device can only decode its hardware resources if both bits 0 <strong>and</strong> 1 are set. If the device is not<br />

present (bit 0 cleared) or not enabled (bit 1 cleared), then the device must not decode its resources.<br />

If a device is present in the machine, but should not be displayed in OSPM user interface, bit 2 is<br />

cleared. For example, a notebook could have joystick hardware (thus it is present <strong>and</strong> decoding its<br />

resources), but the connector for plugging in the joystick requires a port replicator. If the port<br />

replicator is not plugged in, the joystick should not appear in the UI, so bit 2 is cleared.<br />

_STA may return bit 0 clear (not present) with bit 3 set (device is functional). This case is used to<br />

indicate a valid device for which no device driver should be loaded (for example, a bridge device.)<br />

Children of this device may be present <strong>and</strong> valid. OSPM should continue enumeration below a<br />

device whose _STA returns this bit combination.<br />

If a device object (including the processor object) does not have an _STA object, then OSPM<br />

assumes that all of the above bits are set (i.e., the device is present, enabled, shown in the UI, <strong>and</strong><br />

functioning).<br />

6.4 Resource Data Types for ACPI<br />

The _CRS, _PRS, <strong>and</strong> _SRS control methods use packages of resource descriptors to describe the<br />

resource requirements of devices.<br />

6.4.1 ASL Macros for Resource Descriptors<br />

ASL includes some macros for creating resource descriptors. The ASL syntax for these macros is<br />

defined in Section 19.5, “ASL Operator Reference”, along with the other ASL operators.<br />

6.4.2 Small Resource Data Type<br />

A small resource data type may be 2 to 8 bytes in size <strong>and</strong> adheres to the following format:<br />

Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba 309

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

Saved successfully!

Ooh no, something went wrong!