Under most circumstances, when the USB stack receives this request, it both sets the remote wake-up feature on the device and puts the device to sleep by suspending the device's upstream port. Instead, it waits until it receives a IRP_MN_SET_POWER request to change the WDM device state of the device to D1/D2. The USB specification specifies that host software must set the remote wake-up feature on a device 'only just prior' to putting the device to sleep.įor this reason, the USB stack does not set the DEVICE_REMOTE_WAKEUP feature on a device after receiving a wait wake IRP for the device. In USB terminology, a USB device is enabled for remote wake-up when its DEVICE_REMOTE_WAKEUP feature is set. The wait wake mechanism is described in the section Supporting Devices That Have Wake-Up Capabilities.

Devices that are not capable of generating remote wake signaling include video cameras, mass storage devices, audio devices, and printers.ĭrivers for devices that support remote wake-up signaling must issue an IRP_MN_WAIT_WAKE IRP, also known as a wait wake IRP, to arm the device for remote wake-up. All of these devices are capable of producing remote wake signaling. Examples of devices that have a remote wake-up capability are mice, keyboards, USB hubs, modems (wake on ring), NICs, wake on cable insertion. USB devices that can respond to external wake signals while suspended are said to have a remote wake-up capability.

Remote wake up from internet