/Linux-v4.19/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-v4.19/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-v4.19/Documentation/devicetree/bindings/watchdog/ |
D | samsung-wdt.txt | 3 The Samsung's Watchdog controller is used for resuming system operation
|
/Linux-v4.19/drivers/s390/cio/ |
D | io_sch.h | 151 unsigned int resuming:1; /* recognition while resume */ member
|
D | device.c | 1388 if (cdev->online && !cdev->private->flags.resuming) in sch_get_action() 1480 if (cdev->private->flags.resuming) { in io_subchannel_sch_event() 1497 if (!cdev || !cdev->private->flags.resuming) in io_subchannel_sch_event() 1865 cdev->private->flags.resuming = 1; in __ccw_device_pm_restore() 1885 cdev->private->flags.resuming = 0; in __ccw_device_pm_restore()
|
D | device_fsm.c | 221 if (cdev->private->flags.resuming) { in ccw_device_recog_done()
|
/Linux-v4.19/include/linux/ |
D | visorbus.h | 240 bool resuming; member
|
/Linux-v4.19/Documentation/cgroup-v1/ |
D | freezer-subsystem.txt | 20 and resuming tasks in userspace. Both of these signals are observable 45 have a problem with this method of stopping and resuming tasks.
|
/Linux-v4.19/Documentation/devicetree/bindings/powerpc/fsl/ |
D | pmc.txt | 41 supports disabling and resuming devices at any time.
|
/Linux-v4.19/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-v4.19/arch/sh/kernel/cpu/sh3/ |
D | swsusp.S | 103 ldc r1, spc ! setup pc value for resuming
|
/Linux-v4.19/Documentation/power/ |
D | suspend-and-interrupts.txt | 28 of resuming devices (that is, before starting to execute ->resume_early 36 suspend-resume cycle, including the "noirq" phases of suspending and resuming
|
D | userland-swsusp.txt | 140 The suspending and resuming utilities MUST lock themselves in memory, 166 The resuming utility SHOULD NOT attempt to mount any file systems that could
|
D | swsusp.txt | 84 to standby mode. Later resuming the machine the saved state is loaded back to 95 the resuming. If the option ``hibernate=nocompress'' is specified as a boot 227 Q: After resuming, system is paging heavily, leading to very bad interactivity. 414 before suspending; then remount them after resuming.
|
D | swsusp-dmcrypt.txt | 128 regardless if resuming or not, otherwise later suspend will fail.
|
/Linux-v4.19/drivers/usb/gadget/udc/ |
D | dummy_hcd.c | 256 unsigned resuming:1; member 447 dum_hcd->resuming = 0; in set_link_state() 877 dum_hcd->resuming = 1; in dummy_wakeup() 2006 if (dum_hcd->resuming && time_after_eq(jiffies, dum_hcd->re_timeout)) { in dummy_hub_status() 2105 dum_hcd->resuming = 1; in dummy_hub_control() 2159 if (dum_hcd->resuming && in dummy_hub_control()
|
/Linux-v4.19/net/mac80211/ |
D | util.c | 738 if (local->quiescing || (local->suspended && !local->resuming)) { in ieee80211_can_queue_work() 1759 local->resuming = false; in ieee80211_handle_reconfig_failure() 1884 local->resuming = true; in ieee80211_reconfig() 1897 local->resuming = false; in ieee80211_reconfig() 1958 WARN_ON(local->resuming); in ieee80211_reconfig() 2206 if (!local->resuming) in ieee80211_reconfig() 2243 local->resuming = false; in ieee80211_reconfig() 2277 if (WARN_ON(!local->resuming)) in ieee80211_resume_disconnect()
|
/Linux-v4.19/Documentation/arm/Samsung-S3C24XX/ |
D | Suspend.txt | 44 to say that its bootloader is capable of resuming. This can be as
|
/Linux-v4.19/Documentation/userspace-api/ |
D | seccomp_filter.rst | 112 dependent value -- if resuming execution, set it to something 245 emulation security checks, making resuming the syscall mostly
|
/Linux-v4.19/Documentation/driver-api/pm/ |
D | devices.rst | 271 Suspending or resuming the system is done in several phases. Different phases 418 low-power state. Instead, the PM core will unwind its actions by resuming all 425 When resuming from freeze, standby or memory sleep, the phases are: 581 Resuming from hibernation is, again, more complicated than resuming from a sleep 594 in resuming from hibernation. In fact, the restore kernel may be completely 765 the state of devices (possibly except for resuming them from runtime suspend)
|
/Linux-v4.19/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. 429 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-v4.19/drivers/acpi/ |
D | ec.c | 940 static void acpi_ec_start(struct acpi_ec *ec, bool resuming) in acpi_ec_start() argument 948 if (!resuming) { in acpi_ec_start()
|
/Linux-v4.19/kernel/power/ |
D | Kconfig | 70 Right now you may boot without resuming and resume later but in the
|