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

Return Value Information<br />

Package {<br />

LanguageDescriptor[0]<br />

// Package<br />

}<br />

LanguageDescriptor[n]<br />

// Package<br />

Each Language Descriptor sub-Package contains the elements described below:<br />

Package {<br />

LanguageId<br />

UnicodeDescription<br />

}<br />

// String<br />

// Buffer<br />

LanguageId is a string identifying the language. This string follows the format specified in the<br />

Internet RFC 3066 document (Tags for the Identification of Languages). In addition to supporting<br />

the existing strings in RFC 3066, Table 6-169 lists aliases that are also supported.<br />

Table 6-169 Additional Language ID Alias Strings<br />

RFC String<br />

zh-Hans<br />

zh-Hant<br />

Supported Alias String<br />

zh-chs<br />

zh-cht<br />

UnicodeDescription is a Buffer containing a Unicode (UTF-16) string. This string contains the<br />

language-specific description of the device corresponding to the LanguageID. The Unicode() ASL<br />

macro can be used to create this Buffer.<br />

Example:<br />

Device (XYZ) {<br />

Name (_ADR, 0x00020001)<br />

Name ( _MLS, Package(){(2){“en”, Unicode("ACME super DVD controller")}})<br />

}<br />

6.1.8 _PLD (Physical Location of Device)<br />

This optional object is a method that conveys to OSPM a general description of the physical location<br />

of a device’s external connection point. The _PLD may be child object for any ACPI Namespace<br />

object the system wants to describe. This information can be used by system software to describe to<br />

the user which specific connector or device input mechanism may be used for a given task or may<br />

need user intervention for correct operation. The _PLD should only be evaluated when its parent<br />

device is present as indicated by the device’s presence mechanism (i.e. _STA or other)<br />

An externally exposed device connection point can reside on any surface of a system’s housing. The<br />

respective surfaces of a system’s housing are identified by the “Panel” field (described below). The<br />

_PLD method returns data to describe the location of where the device’s connection point resides<br />

<strong>and</strong> a Shape (described below) that may be rendered at that position. One physical device may have<br />

several connection points. A _PLD describes the offset <strong>and</strong> rotation of a single device connection<br />

point from an “origin” that resides in the lower left h<strong>and</strong> corner of its Panel.<br />

All Panel references (Top, Bottom, Right, Left, etc.) are interpreted as though the user is facing the<br />

front of the system. For h<strong>and</strong>held mobile devices, the front panel is the one holding the display<br />

Version 6.0 283

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

Saved successfully!

Ooh no, something went wrong!