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

Example ASL:<br />

Name (_SUB, "MSFT3000")// Vendor-defined subsystem<br />

6.1.10 _STR (String)<br />

The _STR object evaluates to a Unicode string that describes the device. It may be used by an OS to<br />

provide information to an end user. This information is particularly valuable when no other<br />

information is available.<br />

Arguments:<br />

None<br />

Return Value:<br />

A Buffer containing a Unicode string that describes the device<br />

Example ASL:<br />

Device (XYZ) {<br />

Name (_ADR, 0x00020001)<br />

Name (_STR, Unicode ("ACME super DVD controller"))<br />

}<br />

Then, when all else fails, an OS can use the info included in the _STR object to describe the<br />

hardware to the user.<br />

6.1.11 _SUN (Slot User Number)<br />

_SUN is an object that evaluates to the slot-unique ID number for a slot. _SUN is used by OSPM UI<br />

to identify slots for the user. For example, this can be used for battery slots, PCI slots, PCMCIA<br />

slots, or swappable bay slots to inform the user of what devices are in each slot. _SUN evaluates to<br />

an integer that is the number to be used in the user interface.<br />

Arguments:<br />

None<br />

Return Value:<br />

An Integer containing the slot’s unique ID<br />

The _SUN value is required to be unique among the slots of the same type. It is also recommended<br />

that this number match the slot number printed on the physical slot whenever possible.<br />

6.1.12 _UID (Unique ID)<br />

This object provides OSPM with a logical device ID that does not change across reboots. This object<br />

is optional, but is required when the device has no other way to report a persistent unique device ID.<br />

The _UID must be unique across all devices with either a common _HID or _CID. This is because a<br />

device needs to be uniquely identified to the OSPM, which may match on either a _HID or a _CID to<br />

identify the device. The uniqueness match must be true regardless of whether the OSPM uses the<br />

_HID or the _CID. OSPM typically uses the unique device ID to ensure that the device-specific<br />

information, such as network protocol binding information, is remembered for the device even if its<br />

relative location changes. For most integrated devices, this object contains a unique identifier.<br />

Version 6.0 293

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

Saved successfully!

Ooh no, something went wrong!