Lines Matching refs:wakeup

35 	Some drivers can manage hardware wakeup events, which make the system
37 	using the relevant /sys/devices/.../power/wakeup file (for Ethernet
68 for wakeup events), no more data read or written, and requests from upstream
72 Examples of hardware wakeup events include an alarm from a real time clock,
150 /sys/devices/.../power/wakeup files
153 of system wakeup events (hardware signals that can force the system out of a
159 physically support wakeup events.  The device_set_wakeup_capable() routine
160 affects this flag.  The "power.wakeup" field is a pointer to an object of type
162 its system wakeup mechanism and for notifying the PM core of system wakeup
163 events signaled by the device.  This object is only present for wakeup-capable
167 Whether or not a device is capable of issuing wakeup events is a hardware
169 whether or not a wakeup-capable device should issue wakeup events is a policy
171 "power/wakeup" file.  User space can write the strings "enabled" or "disabled"
173 system wakeup.  This file is only present if the "power.wakeup" object exists
178 The "power/wakeup" file is supposed to contain the "disabled" string initially
182 wakeup requests on their own but merely forward wakeup requests from one bus to
185 The device_may_wakeup() routine returns true only if the "power.wakeup" object
186 exists and the corresponding "power/wakeup" file contains the string "enabled".
188 whether or not to enable the devices' wakeup mechanisms.  If device wakeup
194 It ought to be noted that system wakeup is conceptually different from "remote
195 wakeup" used by runtime power management, although it may be supported by the
196 same physical mechanism.  Remote wakeup is a feature allowing devices in
199 be used to signal system wakeup events, depending on the hardware design.  On
201 case, remote wakeup should always be enabled for runtime power management for
233 system-specific.  Also, wakeup-enabled devices will usually stay partly
245 More power-aware drivers might prepare the devices for triggering system wakeup
347 	and they may enable wakeup events.
375 generating hardware wakeup signals to trigger a system wakeup event when the
484 	prepared to generate wakeup events.
488 	should not be allowed to generate wakeup events by it.
492 	state and should not be allowed to generate wakeup events.
635 PCI device may not perform DMA or issue IRQs, and any wakeup events it
640 wakeup event sources (so drivers would call enable_irq_wake) and might
641 be able to treat DMA completion as a wakeup event (sometimes DMA can stay
690 state temporarily, for example so that its system wakeup capability can be