Lines Matching refs:into

28 devices into states in which they draw less power (low-power states) at the
31 Usually, a device is put into a low-power state when it is underutilized or
33 again, it has to be put back into the "fully functional" state (full-power
38 PCI devices may be put into low-power states in two ways, by using the device
43 specific value into one of its standard configuration registers.  The second
50 to put the device that sent it into the full-power state.  However, the PCI Bus
88 programmed to go into it.  The second one, D3cold, is the state that PCI devices
90 to program a PCI device to go into D3cold, although there may be a programmable
91 interface for putting the bus the device is on into a state in which Vcc is
107 programmatically put into D0.  Thus the kernel can switch the device back and
145 putting a device into a low-power state.  These control methods are encoded
148 them as needed using an AML interpreter that translates the AML byte code into
153 ACPI control methods may be divided into global control methods, that are not
158 ACPI methods used for device power management fall into that category.
163 into account by ACPI).  Moreover, for each power state of a device there is a
164 set of power resources that have to be enabled for the device to be put into
169 To put a device into the ACPI power state Dx (where x is a number between 0 and
173 is going to be put into a low-power state (D1-D3) and is supposed to generate
179 only be put into D0 this way.
182 system-wide transition into a sleep state or back into the working state.  ACPI
186 into and the kernel is supposed to obtain this information by executing the
189 lowest power (highest number) state it can be put into is also determined by the
199 putting the device into a low-power state, have to be caught and handled as
201 (ACPI S0), they should be translated into interrupts so that the kernel can
202 put the devices generating them into the full-power state and take care of the
207 converted into ACPI General-Purpose Events (GPEs) which are hardware signals
240 a native mechanism for converting native PCI PMEs into interrupts generated by
366 First, a PCI device is put into a low-power state, or suspended, with the help
372 the device is prepared to generate wakeup signals and, finally, it is put into
375 The low-power state to put the device into is the lowest-power (highest number)
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
388 A suspended device is brought back into the "active" state, or resumed,
393 back into the full-power state, prevents it from signaling wakeup while in that
402 is handled in one of the ways described in Section 1 and finally converted into
429 When the system is going into a sleep state in which the contents of memory will
440 The pci_pm_prepare() routine first puts the device into the "fully functional"
474 saves them, prepares the device to signal wakeup (if necessary) and puts it into
477 The low-power state to put the device into is the lowest-power (highest number)
486 into low-power states.  However, if one of the driver's suspend callbacks
489 to signal wakeup and put into a low-power state by the driver (the driver is
498 S1-S3, into the working state (ACPI S0), the phases are:
509 The pci_pm_resume_noirq() routine first puts the device into the full-power
544 a system image to be created and written into a persistent storage medium.  The
572 device for signaling wakeup and put it into a low-power state.  Still, it saves
592 but it doesn't put the device into the full power state and doesn't attempt to
622 System restore requires a hibernation image to be loaded into memory and the
627 into memory by a fresh instance of the kernel, called the boot kernel, which in
705 has just been loaded into memory.
723 This callback is expected to quiesce the device and prepare it to be put into a
727 put it into a low-power state.  All of these operations can very well be taken
733 registers, to prepare it for system wakeup (if necessary), and to put it into a
760 after a system image has been loaded into memory from persistent storage and the
765 the driver takes the responsibility for putting the device into a low-power
769 or put it into a low-power state.  Still, either it or freeze_noirq() should
777 after a system image has been loaded into memory and after prepare() and
798 into a low-power state itself instead of allowing the PCI subsystem to do that,
801 into a low-power state, respectively, but it need not save the device's standard
823 Since the PCI subsystem unconditionally puts all devices into the full power
899 It also may be executed if the loading of a hibernation image into memory fails
910 device is about to be suspended (i.e. quiesced and put into a low-power state)
914 put into a low-power state, but it must allow the PCI subsystem to perform all
921 (i.e. put into the full-power state and programmed to process I/O normally) at
925 device after it has been put into the full-power state by the PCI subsystem.
1025 by work items put into the power management workqueue, pm_wq.  Although there
1035 request into pm_wq.  In the majority of cases this also is done by their