Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification
device from DOCK2’s list of ejection dependencies. Starting in ACPI 2.0, OSPM is presented with
a more in-depth view of the ejection dependencies in a system by use of the _EDL methods.
Example
An example use of _EJD and _EDL is as follows:
Scope(\_SB.PCI0) {
Device(DOCK1) {
Name(_ADR, …)
Method(_EJ0, 0) {…}
Method(_DCK, 1) {…}
Name(_BDN, …)
Method(_STA, 0) {0xF}
Name(_EDL, Package( ) {
\_SB.PCI0.IDE2,
\_SB.PCI0.CB2})
}
Device(DOCK2) {
Name(_ADR, …)
Method(_EJ0, 0) {…}
Method(_DCK, 1) {…}
Name(_BDN, …)
Method(_STA, 0) {0x0}
Name(_EDL, Package( ) {
\_SB.PCI0.IDE2})
}
Device(IDE1) {
Name(_ADR, …)
}
Device(IDE2) {
Name(_ADR, …)
Name(_EJD,”\\_SB.PCI0.DOCK1”)
}
// Pass through dock – DOCK1
// DOCK1 has two dependent devices – IDE2 and CB2
// Pass through dock – DOCK2
// DOCK2 has one dependent device – IDE2
// IDE Drive1 not dependent on the dock
// IDE Drive2
// Dependent on DOCK1
Device(CB2) {
// CardBus Controller
Name(_ADR, …)
Name(_EJD,”\\_SB.PCI0.DOCK1”) // Dependent on DOCK1
}
} // end \_SB.PCIO
6.3.3 _EJx (Eject)
These control methods are optional and are supplied for devices that support a software-controlled
VCR-style ejection mechanism or that require an action be performed such as isolation of power/
data lines before the device can be removed from the system. To support warm (system is in a sleep
state) and hot (system is in S0) removal, an _EJx control method is listed for each sleep state from
which the device supports removal, where x is the sleeping state supported. For example, _EJ0
indicates the device supports hot removal; _EJ1–EJ4 indicate the device supports warm removal.
Arguments: (1)
Arg0 – An Integer containing a device ejection control
0 – Cancel a mark for ejection request (EJ0 will never be called with this value)
1 – Hot eject or mark for ejection
334 April, 2015 Version 6.0