| /Linux-v5.4/arch/powerpc/platforms/pseries/ |
| D | suspend.c | 22 static atomic_t suspending; variable
64 if (atomic_read(&suspending)) in pseries_suspend_cpu()
96 atomic_set(&suspending, 0); in pseries_suspend_enter()
109 atomic_set(&suspending, 1); in pseries_prepare_late()
|
| /Linux-v5.4/drivers/crypto/ccp/ |
| D | ccp-dev.c | 325 if (!ccp->suspending) { in ccp_enqueue_cmd()
385 if (ccp->suspending) { in ccp_dequeue_cmd()
564 ccp->suspending = 1; in ccp_dev_suspend()
592 ccp->suspending = 0; in ccp_dev_resume()
|
| D | ccp-dev.h | 428 unsigned int suspending; member
|
| /Linux-v5.4/Documentation/power/ |
| D | basic-pm-debugging.rst | 19 because some problems only show up on a second attempt at suspending and
56 - test the freezing of processes and suspending of devices
59 - test the freezing of processes, suspending of devices and platform
63 - test the freezing of processes, suspending of devices, platform
67 - test the freezing of processes, suspending of devices, platform global
68 control methods\ [1]_, the disabling of nonboot CPUs and suspending
78 suspending devices) and issue the standard hibernation commands. For example,
89 /sys/power/pm_test , then after suspending devices the kernel will additionally
147 If the "core" test fails, which means that suspending of the system/platform
|
| D | userland-swsusp.rst | 158 The suspending and resuming utilities MUST lock themselves in memory,
161 The suspending utility MUST check the value stored by SNAPSHOT_CREATE_IMAGE
168 (a) The suspending utility MUST NOT close the snapshot device
171 suspending utility SHOULD destroy it, preferably by zapping
175 (b) The suspending utility SHOULD NOT attempt to perform any
183 the snapshot image), the suspending utility MUST close the snapshot
|
| D | swsusp-and-swap-files.rst | 58 /proc/swaps) so that it can be used for suspending.
60 Note that if the swap file used for suspending is deleted and recreated,
|
| D | suspend-and-interrupts.rst | 13 suspend after the "late" phase of suspending devices (that is, after all of the
38 suspend-resume cycle, including the "noirq" phases of suspending and resuming
101 interrupts right after the "noirq" phase of suspending devices.
|
| D | swsusp.rst | 133 well, suspending a server is IMHO a really stupid thing,
163 during suspending, but otherwise it would work...
465 before suspending; then remount them after resuming.
|
| D | freezing-of-tasks.rst | 131 from interfering with the suspending and resuming of devices. A user space
132 process running on a second CPU while we are suspending devices may, for
|
| D | video.rst | 85 your video card (good luck getting docs :-(). Maybe suspending from X
|
| /Linux-v5.4/drivers/input/touchscreen/ |
| D | zforce_ts.c | 117 bool suspending; member
502 if (!ts->suspending && device_may_wakeup(&client->dev)) in zforce_irq_thread()
530 if (ts->suspending && device_may_wakeup(&client->dev)) in zforce_irq_thread()
583 if (!ts->suspending && device_may_wakeup(&client->dev)) in zforce_irq_thread()
619 ts->suspending = true; in zforce_suspend()
650 ts->suspending = false; in zforce_suspend()
|
| /Linux-v5.4/drivers/tty/serial/ |
| D | max3100.c | 125 int suspending; member
177 if (!s->force_end_work && !freezing(current) && !s->suspending) in max3100_dowork()
551 if (s->suspending) in max3100_shutdown()
591 if (s->suspending) in max3100_startup()
853 s->suspending = 1; in max3100_suspend()
877 s->suspending = 0; in max3100_resume()
|
| /Linux-v5.4/drivers/usb/serial/ |
| D | usb-serial.c | 1117 serial->suspending = 1; in usb_serial_suspend()
1127 serial->suspending = 0; in usb_serial_suspend()
1154 serial->suspending = 0; in usb_serial_resume()
1171 serial->suspending = 0; in usb_serial_reset_resume()
|
| /Linux-v5.4/arch/arm/mach-pxa/ |
| D | sleep.S | 103 @ about suspending with PXBus operating above 133MHz
|
| /Linux-v5.4/include/linux/usb/ |
| D | serial.h | 152 unsigned char suspending:1; member
|
| /Linux-v5.4/drivers/usb/host/ |
| D | ehci-hub.c | 148 bool suspending, bool do_wakeup) in ehci_adjust_port_wakeup_flags() argument
186 if (!suspending) { in ehci_adjust_port_wakeup_flags()
207 if (!suspending && ehci_port_change(ehci)) in ehci_adjust_port_wakeup_flags()
|
| D | ehci.h | 889 bool suspending, bool do_wakeup);
|
| /Linux-v5.4/Documentation/arm/samsung-s3c24xx/ |
| D | suspend.rst | 88 suspending, which means that use of printascii() or similar direct
|
| /Linux-v5.4/kernel/power/ |
| D | Kconfig | 73 suspending. Also in this case you must not use the filesystems
93 on before suspending.
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | power-management.rst | 33 Power Management (PM) is the practice of saving energy by suspending
288 device by suspending it at the wrong time. (Highly unlikely, but
342 suspending the other interfaces. The USB core doesn't allow this; all
433 suspending and resuming correctly. This is exactly equivalent to
516 the system is suspending. The remote wakeup may succeed, which would
565 In addition to suspending endpoint devices and enabling hardware
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 33 runtime idle by freezing user space, suspending the timekeeping and putting all
57 In addition to freezing user space, suspending the timekeeping and putting all
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | device_link.rst | 13 hierarchy: When suspending, resuming or shutting down the system, devices
92 can be specified to runtime resume the supplier and prevent it from suspending
|
| /Linux-v5.4/Documentation/networking/device_drivers/intel/ |
| D | igb.rst | 138 prior to shutting down or suspending the system.
|
| /Linux-v5.4/drivers/acpi/ |
| D | ec.c | 983 static void acpi_ec_stop(struct acpi_ec *ec, bool suspending) in acpi_ec_stop() argument
995 if (!suspending) { in acpi_ec_stop()
|
| /Linux-v5.4/drivers/bluetooth/ |
| D | btusb.c | 1413 bool suspending; in submit_or_queue_tx_urb() local
1416 suspending = test_bit(BTUSB_SUSPENDING, &data->flags); in submit_or_queue_tx_urb()
1417 if (!suspending) in submit_or_queue_tx_urb()
1421 if (!suspending) in submit_or_queue_tx_urb()
|
