| /linux/Documentation/admin-guide/pm/ |
| H A D | suspend-flows.rst | 126 1. Resuming timekeeping and unfreezing the scheduler tick.
137 2. Resuming devices and restoring the working-state configuration of IRQs.
247 2. Resuming core system components.
257 4. Resuming devices and restoring the working-state configuration of IRQs.
|
| /linux/Documentation/power/ |
| H A D | suspend-and-interrupts.rst | 9 Suspending and Resuming Device IRQs
30 of resuming devices (that is, before starting to execute ->resume_early
38 suspend-resume cycle, including the "noirq" phases of suspending and resuming
|
| H A D | swsusp.rst | 94 to standby mode. Later resuming the machine the saved state is loaded back to
105 the resuming. If the option `hibernate=nocompress` is specified as a boot
257 After resuming, system is paging heavily, leading to very bad interactivity.
467 before suspending; then remount them after resuming.
|
| H A D | userland-swsusp.rst | 160 The suspending and resuming utilities MUST lock themselves in memory,
189 The resuming utility SHOULD NOT attempt to mount any file systems that could
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | freezer-subsystem.rst | 24 and resuming tasks in userspace. Both of these signals are observable
49 have a problem with this method of stopping and resuming tasks.
|
| /linux/net/bluetooth/ |
| H A D | msft.c | 129 __u8 resuming; member
591 msft->resuming = true; in reregister_monitor()
604 msft->resuming = false; in reregister_monitor()
658 msft->resuming = true; in msft_do_open()
1159 if (msft->resuming || msft->suspending) in msft_add_monitor_pattern()
1173 if (msft->resuming || msft->suspending) in msft_remove_monitor()
|
| /linux/drivers/mfd/ |
| H A D | max77686.c | 238 * while suspended it will be handled before resuming I2C. in max77686_suspend()
241 * an interrupt occurs before resuming I2C bus controller. in max77686_suspend()
|
| /linux/arch/arm/mach-s3c/ |
| H A D | pm-core-s3c64xx.h | 62 * problems between going to sleep and resuming. in samsung_pm_saved_gpios()
|
| H A D | irq-pm-s3c64xx.c | 87 S3C_PMDBG("%s: resuming IRQs\n", __func__); in s3c64xx_irq_pm_resume()
|
| /linux/drivers/vfio/ |
| H A D | debugfs.c | 43 seq_puts(seq, "RESUMING\n"); in vfio_device_state_read()
|
| /linux/tools/testing/selftests/kvm/x86_64/ |
| H A D | hyperv_evmcs.c | 130 * NMI forces L2->L1 exit, resuming L2 and hope that EVMCS is in guest_code()
288 /* Force immediate L2->L1 exit before resuming */ in main()
|
| H A D | vmx_apic_access_test.c | 15 * this situation, so resuming L2 should result in a KVM exit for
|
| /linux/drivers/thermal/ |
| H A D | thermal_core.h | 104 * @resuming: indicates whether or not thermal zone resume is in progress
138 bool resuming; member
|
| /linux/Documentation/devicetree/bindings/dma/ |
| H A D | sprd,sc9860-dma.yaml | 12 system power without resuming system by DMA interrupts if AGCP DMA
|
| /linux/scripts/gdb/linux/ |
| H A D | genpd.py | 31 "resuming",
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | pmc.txt | 41 supports disabling and resuming devices at any time.
|
| /linux/Documentation/devicetree/bindings/watchdog/ |
| H A D | samsung-wdt.yaml | 13 The Samsung's Watchdog controller is used for resuming system operation
|
| /linux/arch/arm/mach-pxa/ |
| H A D | pxa3xx.c | 99 * PXA3xx development kits assumes that the resuming process continues
119 /* resuming from D2 requires the HSIO2/BOOT/TPM clocks enabled */ in pxa3xx_cpu_pm_suspend()
|
| /linux/Documentation/driver-api/usb/ |
| H A D | power-management.rst | 74 However some devices have the capability of resuming by themselves, or
80 event. Examples include a suspended keyboard resuming when a key is
81 pressed, or a suspended USB hub resuming when a device is plugged in.
433 suspending and resuming correctly. This is exactly equivalent to
682 Resuming the child device when the parent port regains power resolves those
|
| /linux/drivers/usb/host/ |
| H A D | uhci-hub.c | 38 /* suspend/resume bits: port suspended or port resuming */
175 * after the resuming period is over. */ in uhci_check_ports()
|
| /linux/drivers/scsi/isci/ |
| H A D | remote_device.h | 184 * An indication that the device is resuming operation. SCI_SUCCESS the device
185 * is resuming operation.
|
| /linux/arch/arm/kernel/ |
| H A D | suspend.c | 46 * the MMU-enable code, required for resuming. On successful in cpu_suspend()
|
| /linux/drivers/usb/usbip/ |
| H A D | vhci.h | 108 unsigned resuming:1; member
|
| /linux/Documentation/driver-api/pm/ |
| H A D | devices.rst | 269 Suspending or resuming the system is done in several phases. Different phases
420 low-power state. Instead, the PM core will unwind its actions by resuming all
427 When resuming from freeze, standby or memory sleep, the phases are:
585 Resuming from hibernation is, again, more complicated than resuming from a sleep
598 in resuming from hibernation. In fact, the restore kernel may be completely
|
| /linux/arch/arm/include/asm/ |
| H A D | tls.h | 90 * thread_info upon resuming execution and the following mcr in set_tls()
|