| /Linux-v5.10/Documentation/admin-guide/pm/ |
| 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-v5.10/Documentation/power/ |
| 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
|
| 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.
|
| 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-v5.10/Documentation/arm/samsung-s3c24xx/ |
| D | suspend.rst | 28 Resuming section in S3C24XX Suspend Support
45 to say that its bootloader is capable of resuming. This can be as
|
| /Linux-v5.10/Documentation/admin-guide/cgroup-v1/ |
| 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-v5.10/Documentation/devicetree/bindings/watchdog/ |
| D | samsung-wdt.yaml | 13 The Samsung's Watchdog controller is used for resuming system operation
|
| /Linux-v5.10/drivers/mfd/ |
| D | max77686.c | 241 * while suspended it will be handled before resuming I2C. in max77686_suspend()
244 * an interrupt occurs before resuming I2C bus controller. in max77686_suspend()
|
| /Linux-v5.10/arch/arm/mach-s3c/ |
| D | pm-core-s3c64xx.h | 79 * problems between going to sleep and resuming. in samsung_pm_saved_gpios()
|
| D | irq-pm-s3c64xx.c | 87 S3C_PMDBG("%s: resuming IRQs\n", __func__); in s3c64xx_irq_pm_resume()
|
| /Linux-v5.10/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 41 supports disabling and resuming devices at any time.
|
| /Linux-v5.10/scripts/gdb/linux/ |
| D | genpd.py | 31 "resuming",
|
| /Linux-v5.10/arch/arm/kernel/ |
| D | suspend.c | 30 * the MMU-enable code, required for resuming. On successful in cpu_suspend()
|
| /Linux-v5.10/drivers/scsi/isci/ |
| D | remote_device.h | 184 * An indication that the device is resuming operation. SCI_SUCCESS the device
185 * is resuming operation.
|
| /Linux-v5.10/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-pmc.yaml | 119 by AVP when resuming from the LP0 state.
124 some PLLs, clocks and then brings up CPU0 for resuming the
|
| /Linux-v5.10/include/linux/ |
| D | visorbus.h | 213 * @resuming: Indicates that a change towards a running state
240 bool resuming; member
|
| /Linux-v5.10/drivers/usb/host/ |
| 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-v5.10/arch/arm/include/asm/ |
| D | tls.h | 75 * thread_info upon resuming execution and the following mcr
|
| /Linux-v5.10/drivers/usb/usbip/ |
| D | vhci.h | 108 unsigned resuming:1; member
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| 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-v5.10/Documentation/driver-api/pm/ |
| 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-v5.10/drivers/gpu/drm/nouveau/ |
| D | nouveau_drm.c | 875 NV_DEBUG(drm, "resuming display...\n"); in nouveau_do_suspend()
887 NV_DEBUG(drm, "resuming object tree...\n"); in nouveau_do_resume()
894 NV_DEBUG(drm, "resuming fence...\n"); in nouveau_do_resume()
901 NV_DEBUG(drm, "resuming display...\n"); in nouveau_do_resume()
903 NV_DEBUG(drm, "resuming console...\n"); in nouveau_do_resume()
|
| /Linux-v5.10/drivers/visorbus/ |
| D | visorbus_main.c | 1114 if (!dev->resuming) in resume_state_change_complete()
1117 dev->resuming = false; in resume_state_change_complete()
1147 if (dev->pausing || dev->resuming) in visorchipset_initiate_device_pause_resume()
1160 dev->resuming = true; in visorchipset_initiate_device_pause_resume()
1200 dev_info->resuming = false; in visorchipset_device_resume()
|
| /Linux-v5.10/arch/arm/mach-pxa/ |
| D | pxa3xx.c | 94 * PXA3xx development kits assumes that the resuming process continues
110 /* resuming from D2 requires the HSIO2/BOOT/TPM clocks enabled */ in pxa3xx_cpu_pm_suspend()
|
| /Linux-v5.10/arch/arm64/kernel/ |
| D | suspend.c | 46 * We are resuming from reset with the idmap active in TTBR0_EL1. in __cpu_suspend_exit()
|
