Lines Matching refs:may

36 	leave the low-power state.  This feature may be enabled or disabled
38 	drivers the ioctl interface used by ethtool may also be used for this
39 	purpose); enabling it may cost some power usage, but let the whole
43 	Devices may also be put into low-power states while the system is
48 	device is on, it may be necessary to carry out some bus-specific
50 	states at run time may require special handling during system-wide power
62 have been put into low-power states (at runtime), the effect may be very similar
69 drivers are no longer accepted.  A given bus or platform may have different
195 wakeup" used by runtime power management, although it may be supported by the
198 they should be put into the full-power state.  Those interrupts may or may not
262 In particular, this means that a device registration may fail if the parent of
303 The PM domain, type, class and bus callbacks may in turn invoke device- or
321 	registered at will.  (By contrast, devices may be unregistered at any
325 	After the prepare callback method returns, no new children may be
326 	registered below the device.  The method may also prepare the device or
331 	prepare callback can be used to indicate to the PM core that it may
352 	I/O.  They also may save the device registers and put it into the
354 	and they may enable wakeup events.
379 runtime PM may already have performed some or all of these steps.)
421 	however, that new children may be registered below the device as soon as
426 	the device may have been left in runtime suspend throughout the whole
429 	phases of system resume may have been skipped for it).  In that case,
432 	example, it may need to queue up a runtime resume request for the device
436 	directly after the preceding prepare and special action may be required
443 However, the details here may again be platform-specific.  For example,
451 This may be the hardest part, and the one most protected by NDA'd documents
463 These callbacks may return an error value, but the PM core will ignore such
488 	IRQs or DMA, and they may need to save the values of device registers.
555 resuming from hibernation.  In fact, the boot kernel may be completely different
593 the boot kernel.  Consequently the state of the device may be different from the
595 device may even need to be reset and completely re-initialized.  In many cases
642 PCI device may not perform DMA or issue IRQs, and any wakeup events it
651 Some details here may be platform-specific.  Systems may have devices that
657 Moreover, the specific actions taken may depend on the target system state.
669 To handle these cases, subsystems and device drivers may register power
693 In some cases the decision may be made at the subsystem level while in other
694 cases the device driver may be left to decide.  In some cases it may be