Home
last modified time | relevance | path

Searched full:resuming (Results 1 – 25 of 661) sorted by relevance

12345678910>>...27

/kernel/linux/linux-6.6/Documentation/admin-guide/pm/
Dsuspend-flows.rst126 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.
/kernel/linux/linux-5.10/Documentation/admin-guide/pm/
Dsuspend-flows.rst126 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.
/kernel/linux/linux-5.10/Documentation/power/
Dsuspend-and-interrupts.rst9 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
Dswsusp.rst94 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.
Duserland-swsusp.rst160 The suspending and resuming utilities MUST lock themselves in memory,
189 The resuming utility SHOULD NOT attempt to mount any file systems that could
/kernel/linux/linux-6.6/Documentation/power/
Dsuspend-and-interrupts.rst9 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
Dswsusp.rst94 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.
Duserland-swsusp.rst160 The suspending and resuming utilities MUST lock themselves in memory,
189 The resuming utility SHOULD NOT attempt to mount any file systems that could
/kernel/linux/linux-5.10/Documentation/arm/samsung-s3c24xx/
Dsuspend.rst28 Resuming chapter
45 to say that its bootloader is capable of resuming. This can be as
/kernel/linux/linux-6.6/drivers/vfio/
Dvfio_main.c623 * RESUMING -> STOP in vfio_mig_get_next_state()
624 * STOP -> RESUMING in vfio_mig_get_next_state()
660 * PRE_COPY -> RUNNING -> RUNNING_P2P -> STOP -> RESUMING in vfio_mig_get_next_state()
663 * PRE_COPY_P2P -> RUNNING_P2P -> STOP -> RESUMING in vfio_mig_get_next_state()
664 * RESUMING -> STOP -> RUNNING_P2P in vfio_mig_get_next_state()
665 * RESUMING -> STOP -> RUNNING_P2P -> PRE_COPY_P2P in vfio_mig_get_next_state()
666 * RESUMING -> STOP -> RUNNING_P2P -> RUNNING in vfio_mig_get_next_state()
667 * RESUMING -> STOP -> RUNNING_P2P -> RUNNING -> PRE_COPY in vfio_mig_get_next_state()
668 * RESUMING -> STOP -> STOP_COPY in vfio_mig_get_next_state()
671 * RUNNING -> RUNNING_P2P -> STOP -> RESUMING in vfio_mig_get_next_state()
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/cgroup-v1/
Dfreezer-subsystem.rst24 and resuming tasks in userspace. Both of these signals are observable
49 have a problem with this method of stopping and resuming tasks.
/kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/
Dfreezer-subsystem.rst24 and resuming tasks in userspace. Both of these signals are observable
49 have a problem with this method of stopping and resuming tasks.
/kernel/linux/linux-6.6/net/bluetooth/
Dmsft.c130 __u8 resuming; member
592 msft->resuming = true; in reregister_monitor()
605 msft->resuming = false; in reregister_monitor()
659 msft->resuming = true; in msft_do_open()
1160 if (msft->resuming || msft->suspending) in msft_add_monitor_pattern()
1174 if (msft->resuming || msft->suspending) in msft_remove_monitor()
/kernel/linux/linux-6.6/drivers/mfd/
Dmax77686.c238 * while suspended it will be handled before resuming I2C. in max77686_suspend()
241 * an interrupt occurs before resuming I2C bus controller. in max77686_suspend()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/
Dsamsung-wdt.yaml13 The Samsung's Watchdog controller is used for resuming system operation
/kernel/linux/linux-6.6/arch/arm/mach-s3c/
Dpm-core-s3c64xx.h62 * problems between going to sleep and resuming. in samsung_pm_saved_gpios()
/kernel/linux/linux-5.10/drivers/mfd/
Dmax77686.c241 * while suspended it will be handled before resuming I2C. in max77686_suspend()
244 * an interrupt occurs before resuming I2C bus controller. in max77686_suspend()
/kernel/linux/linux-5.10/arch/arm/mach-s3c/
Dpm-core-s3c64xx.h79 * problems between going to sleep and resuming. in samsung_pm_saved_gpios()
/kernel/linux/linux-6.6/tools/testing/selftests/kvm/x86_64/
Dhyperv_evmcs.c131 * NMI forces L2->L1 exit, resuming L2 and hope that EVMCS is in guest_code()
290 /* Force immediate L2->L1 exit before resuming */ in main()
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/powerpc/fsl/
Dpmc.txt41 supports disabling and resuming devices at any time.
/kernel/linux/linux-5.10/scripts/gdb/linux/
Dgenpd.py31 "resuming",
/kernel/linux/linux-6.6/scripts/gdb/linux/
Dgenpd.py31 "resuming",
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/
Dpmc.txt41 supports disabling and resuming devices at any time.
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/watchdog/
Dsamsung-wdt.yaml13 The Samsung's Watchdog controller is used for resuming system operation
/kernel/linux/linux-6.6/arch/arm/mach-pxa/
Dpxa3xx.c99 * 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()

12345678910>>...27