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.

ACPI-Defined Devices <strong>and</strong> Device-Specific Objects<br />

Device(PRT1) {<br />

Name(_ADR, 0x00000001)<br />

// USB port configuration object. This object returns the system<br />

// specific USB port configuration information for port number 1<br />

// Must match the _UPC declaration for USB0.RHUB.PRT1 as this host<br />

// controller is a companion to the EHCI host controller<br />

// provide physical port location info for port 1<br />

Name( _UPC, Package(){<br />

0xFF,<br />

// Port is connectable<br />

0x00, // Connector type – Type ‘A’<br />

0x00000000, // Reserved 0 – must be zero<br />

0x00000000})<br />

// Reserved 1 – must be zero<br />

// Must match the _PLD declaration for USB0.RHUB.PRT1 as this host<br />

// controller is a companion to the EHCI host controller<br />

Name( _PLD, Package(1) {<br />

Buffer( 0x14) {<br />

0x82,0x00,0x00,0x00, // Revision 2, Ignore color<br />

// Color (ignored), width <strong>and</strong> height not<br />

0x00,0x00,0x00,0x00, // required as this is a st<strong>and</strong>ard USB ‘A’<br />

// type connector<br />

0xa1,0x10,0x00,0x00, // User visible, front panel, Vertical<br />

// lower, horz. Left, shape = horz. Rect.<br />

0x03,0x00,0x00,0x00, // ejectable, requires OPSM eject assistance<br />

0xFF,0xFF,0xFF,0xFF})} // Vert. <strong>and</strong> Horiz. Offsets not supplied<br />

} // Device( PRT1)<br />

//<br />

// Define other ports, control methods, etc<br />

…<br />

…<br />

} // Device( RHUB)<br />

} // Device( USB1)<br />

} // Device( PCI0)<br />

} // Scope( _\SB)<br />

9.14 Device Object Name Collision<br />

Devices containing both _HID <strong>and</strong> _CID may have device specific control methods pertaining to<br />

both the device ID in the _HID <strong>and</strong> the device ID in the _CID. These device specific control<br />

methods are defined by the device owner (a st<strong>and</strong>ard body or a vendor or a group of vendor<br />

partners). Since these object names are not controlled by a central authority, there is a likelihood that<br />

the names of objects will conflict between two defining parties. The _DSM object described in the<br />

next section solves this conflict.<br />

9.14.1 _DSM (Device Specific Method)<br />

This optional object is a control method that enables devices to provide device specific control<br />

functions that are consumed by the device driver.<br />

Arguments: (4)<br />

Arg0 – A Buffer containing a UUID<br />

Arg1 – An Integer containing the Revision ID<br />

Arg2 – An Integer containing the Function Index<br />

Version 6.0 531

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

Saved successfully!

Ooh no, something went wrong!