Advanced Configuration and Power Interface Specification

ACPI-Defined Devices and Device-Specific Objects
Name( _UPC, Package(){
0xFF,
// Port is connectable
0x00, // Connector type – Type ‘A’
0x00000000, // Reserved 0 – must be zero
0x00000000})
// Reserved 1 – must be zero
Name( _PLD, Package(1) {
Buffer(0x14) {
0x82,0x00,0x00,0x00, // Revision 2, Ignore color
// Color (ignored), width and height not
0x00,0x00,0x00,0x00, // required as this is a standard USB ‘A’ type
// connector
0xa1,0x12,0x00,0x00, // User visible, front panel, Vertical
// lower, horz. right, shape = horz. rectangle
0x03,0x00,0x00,0x00, // ejectable, requires OPSM eject assistance
0xFF,0xFF,0xFF,0xFF}) // Vert. and Horiz. Offsets not supplied
} // Device( PRT2)
} // Device( PRT3)
} // Device( RHUB)
9.13.1 USB 2.0 Host Controllers and _UPC and _PLD
Platforms implementing USB2.0 host controllers that consist of one or more USB1.1 compliant
companion controllers (e.g. UHCI or OHCI) must implement a _UPC and a _PLD object for each
port USB port that can be routed between the EHCI host controller and its associated companion
controller. This is required because a USB Port Capabilities object implemented for a port that is a
child of an EHCI host controller may not be available if the OSPM disables the parent host
controller. For example, if root port 1 on an EHCI host controller is routable to root port 1 on its
companion controller, then the namespace must provide a _UPC and a _PLD object under each host
controller’s associated port 1 child object.
Version 6.0 529