PLX USB Device-Side API Developerís Help System
This function wakes up the PLX USB chip from its Low-Power Suspend state.
Points to a Device Object representing the device.
Client calls NcApi_WakeupChip to wakeup a suspended USB chip.
From a programmerís perspective, NcApi_WakeupChip can be called any time, in any context; however, while connected to a suspended host, devices must be cautious about using VBUS power.
Generally, client connected to a suspended USB host calls NcApi_WakeupChip as the first step toward waking the host. After calling NcApi_WakeupChip, client must quickly call NcApi_WakeupHost to generate host Wakeup signaling. (See USB 2.0, Section 220.127.116.11, for important device restrictions on waking suspended hosts.)
The chip can be wakened by the following options:
Client calling NcApi_WakeupChip (applies mostly to self-powered, power-sensitive devices)
Chip Wakeup signal is asserted (applies well to bus-powered devices)
Host resumes signaling (applies to all clients that suspend the chip)
The USB chip requires time to restart its oscillator and to fully wake up. Regardless of the wakeup source, the API uses a device event to signal the client that the chip completed its Wakeup procedure.
Power Management is varied and complex. Refer to the chip and USB 2.0 specifications for important details related to Power Management, Suspend, and Wakeup.
NC_DEVICE_EVENT_CODE | NC_DEVICE_OBJECT | NC_USB_POWER | NcApi_WakeupHost