Lines Matching refs:wakeup

47 Devices supporting the native PCI PM usually can generate wakeup signals called
60 preparing the device to generate wakeup signals.  In that case, however, it
133 sufficiently active to generate a wakeup signal.
174 wakeup signals from that state, the _DSW (or _PSW, replaced with _DSW by ACPI
193 enabled for the device to be able to generate wakeup signals.
204 sleeping, they should cause the system's core logic to trigger wakeup.
206 On ACPI-based systems wakeup signals sent by conventional PCI devices are
211 capable of signaling wakeup.  The information on the connections between GPEs
215 If a PCI device known to the system's ACPI BIOS signals wakeup, the GPE
217 bridges may also be triggered in response to a wakeup signal from one of the
223 the ACPI S1-S4 states), in which case system wakeup is started by its core logic
224 (the device that was the source of the signal causing the system wakeup to occur
226 wakeup GPEs.
233 a PCI device signaling wakeup).  The GPEs used for notifying the kernel of
237 Unfortunately, there is no standard way of handling wakeup signals sent by
339 The second function checks if the device can be prepared to signal wakeup with
341 the function updates the wakeup fields in struct device embedded in the
343 device from signaling wakeup.
361 entire mechanics necessary for handling runtime wakeup signals from PCI devices
363 PCI Express PME signaling and the ACPI GPE-based wakeup signaling described in
372 the device is prepared to generate wakeup signals and, finally, it is put into
376 state from which it can signal wakeup.  The exact method of signaling wakeup is
379 device for signaling wakeup and put it into the selected low-power state, the
384 not attempt to prepare the device for signaling wakeup or to put it into a
393 back into the full-power state, prevents it from signaling wakeup while in that
400 as a result of a wakeup signal from the device itself (this sometimes is
401 referred to as "remote wakeup").  Of course, for this purpose the wakeup signal
474 saves them, prepares the device to signal wakeup (if necessary) and puts it into
478 state from which it can signal wakeup while the system is in the target sleep
480 signaling wakeup is system-dependent and determined by the PCI subsystem, which
481 is also responsible for preparing the device to signal wakeup from the system's
485 generally not expected to prepare devices for signaling wakeup or to put them
489 to signal wakeup and put into a low-power state by the driver (the driver is
529 returned.  Otherwise, the device's wakeup signaling mechanisms are blocked and
572 device for signaling wakeup and put it into a low-power state.  Still, it saves
733 registers, to prepare it for system wakeup (if necessary), and to put it into a
768 In that cases the freeze() callback should not prepare the device system wakeup
800 pci_set_power_state() to prepare the device for system wakeup and to put it