| /Linux-v5.4/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.4/drivers/usb/usbip/ |
| D | vhci.h | 108 unsigned resuming:1; member
|
| D | vhci_hcd.c | 384 vhci_hcd->resuming = 1; in vhci_hub_control()
443 if (vhci_hcd->resuming && time_after(jiffies, vhci_hcd->re_timeout)) { in vhci_hub_control()
446 vhci_hcd->resuming = 0; in vhci_hub_control()
|
| /Linux-v5.4/Documentation/devicetree/bindings/watchdog/ |
| D | samsung-wdt.txt | 3 The Samsung's Watchdog controller is used for resuming system operation
|
| /Linux-v5.4/drivers/s390/cio/ |
| D | io_sch.h | 163 unsigned int resuming:1; /* recognition while resume */ member
|
| D | device.c | 1420 if (cdev->online && !cdev->private->flags.resuming) in sch_get_action()
1512 if (cdev->private->flags.resuming) { in io_subchannel_sch_event()
1529 if (!cdev || !cdev->private->flags.resuming) in io_subchannel_sch_event()
1896 cdev->private->flags.resuming = 1; in __ccw_device_pm_restore()
1916 cdev->private->flags.resuming = 0; in __ccw_device_pm_restore()
|
| D | device_fsm.c | 227 if (cdev->private->flags.resuming) { in ccw_device_recog_done()
|
| /Linux-v5.4/include/linux/ |
| D | visorbus.h | 240 bool resuming; member
|
| /Linux-v5.4/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.4/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 41 supports disabling and resuming devices at any time.
|
| /Linux-v5.4/arch/sh/kernel/cpu/sh3/ |
| D | swsusp.S | 100 ldc r1, spc ! setup pc value for resuming
|
| /Linux-v5.4/Documentation/power/ |
| D | suspend-and-interrupts.rst | 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 | userland-swsusp.rst | 158 The suspending and resuming utilities MUST lock themselves in memory,
187 The resuming utility SHOULD NOT attempt to mount any file systems that could
|
| 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
256 After resuming, system is paging heavily, leading to very bad interactivity.
465 before suspending; then remount them after resuming.
|
| D | swsusp-dmcrypt.rst | 130 regardless if resuming or not, otherwise later suspend will fail.
|
| /Linux-v5.4/drivers/usb/gadget/udc/ |
| D | dummy_hcd.c | 257 unsigned resuming:1; member
448 dum_hcd->resuming = 0; in set_link_state()
864 dum_hcd->resuming = 1; in dummy_wakeup()
2004 if (dum_hcd->resuming && time_after_eq(jiffies, dum_hcd->re_timeout)) { in dummy_hub_status()
2103 dum_hcd->resuming = 1; in dummy_hub_control()
2157 if (dum_hcd->resuming && in dummy_hub_control()
|
| /Linux-v5.4/Documentation/arm/samsung-s3c24xx/ |
| D | suspend.rst | 45 to say that its bootloader is capable of resuming. This can be as
|
| /Linux-v5.4/net/mac80211/ |
| D | util.c | 862 if (local->quiescing || (local->suspended && !local->resuming)) { in ieee80211_can_queue_work()
2022 local->resuming = false; in ieee80211_handle_reconfig_failure()
2147 local->resuming = true; in ieee80211_reconfig()
2160 local->resuming = false; in ieee80211_reconfig()
2221 WARN_ON(local->resuming); in ieee80211_reconfig()
2474 if (!local->resuming) in ieee80211_reconfig()
2515 local->resuming = false; in ieee80211_reconfig()
2549 if (WARN_ON(!local->resuming)) in ieee80211_resume_disconnect()
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-pmc.txt | 52 resuming from the LP0 state. The AVP (Audio-Video Processor) is an ARM7
56 bring up CPU0 for resuming the system.
|
| /Linux-v5.4/Documentation/userspace-api/ |
| D | seccomp_filter.rst | 112 dependent value -- if resuming execution, set it to something
329 emulation security checks, making resuming the syscall mostly
|
| /Linux-v5.4/Documentation/driver-api/pm/ |
| D | devices.rst | 277 Suspending or resuming the system is done in several phases. Different phases
424 low-power state. Instead, the PM core will unwind its actions by resuming all
431 When resuming from freeze, standby or memory sleep, the phases are:
587 Resuming from hibernation is, again, more complicated than resuming from a sleep
600 in resuming from hibernation. In fact, the restore kernel may be completely
771 the state of devices (possibly except for resuming them from runtime suspend)
|
| /Linux-v5.4/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
|
| D | persist.rst | 59 You can check the kernel log after resuming to see if either of these
|
| /Linux-v5.4/drivers/acpi/ |
| D | ec.c | 955 static void acpi_ec_start(struct acpi_ec *ec, bool resuming) in acpi_ec_start() argument
963 if (!resuming) { in acpi_ec_start()
|
| /Linux-v5.4/kernel/power/ |
| D | Kconfig | 71 Right now you may boot without resuming and resume later but in the
|
