| /linux-4.4.14/drivers/usb/usbip/ |
| D | vhci.h | 83 unsigned resuming:1; member
|
| D | vhci_hcd.c | 269 dum->resuming = 1; in vhci_hub_control()
278 dum->resuming = 0; in vhci_hub_control()
322 if (dum->resuming && time_after(jiffies, dum->re_timeout)) { in vhci_hub_control()
327 dum->resuming = 0; in vhci_hub_control()
|
| /linux-4.4.14/Documentation/devicetree/bindings/watchdog/ |
| D | samsung-wdt.txt | 3 The Samsung's Watchdog controller is used for resuming system operation
|
| /linux-4.4.14/drivers/s390/cio/ |
| D | io_sch.h | 149 unsigned int resuming:1; /* recognition while resume */ member
|
| D | device.c | 1431 if (cdev->online && !cdev->private->flags.resuming) in sch_get_action()
1523 if (cdev->private->flags.resuming) { in io_subchannel_sch_event()
1540 if (!cdev || !cdev->private->flags.resuming) in io_subchannel_sch_event()
1905 cdev->private->flags.resuming = 1; in __ccw_device_pm_restore()
1925 cdev->private->flags.resuming = 0; in __ccw_device_pm_restore()
|
| D | device_fsm.c | 260 if (cdev->private->flags.resuming) { in ccw_device_recog_done()
|
| /linux-4.4.14/drivers/staging/unisys/visorbus/ |
| D | visorbus_main.c | 1384 if (!dev->resuming) in resume_state_change_complete()
1387 dev->resuming = false; in resume_state_change_complete()
1419 if (dev->pausing || dev->resuming) in initiate_chipset_device_pause_resume()
1445 dev->resuming = true; in initiate_chipset_device_pause_resume()
1452 dev->resuming = false; in initiate_chipset_device_pause_resume()
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-pmc.txt | 48 resuming from the LP0 state. The AVP (Audio-Video Processor) is an ARM7
52 bring up CPU0 for resuming the system.
|
| /linux-4.4.14/drivers/staging/unisys/include/ |
| D | visorbus.h | 149 bool resuming; member
|
| /linux-4.4.14/Documentation/cgroups/ |
| 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-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 41 supports disabling and resuming devices at any time.
|
| /linux-4.4.14/arch/sh/kernel/cpu/sh3/ |
| D | swsusp.S | 103 ldc r1, spc ! setup pc value for resuming
|
| /linux-4.4.14/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 | 76 to standby mode. Later resuming the machine the saved state is loaded back to
87 the resuming. If the option ``hibernate=nocompress'' is specified as a boot
219 Q: After resuming, system is paging heavily, leading to very bad interactivity.
406 before suspending; then remount them after resuming.
|
| D | swsusp-dmcrypt.txt | 128 regardless if resuming or not, otherwise later suspend will fail.
|
| D | devices.txt | 271 Suspending or resuming the system is done in several phases. Different phases
388 low-power state. Instead the PM core will unwind its actions by resuming all
394 When resuming from freeze, standby or memory sleep, the phases are:
542 Resuming from hibernation is, again, more complicated than resuming from a sleep
555 resuming from hibernation. In fact, the boot kernel may be completely different
|
| D | basic-pm-debugging.txt | 16 resuming the system.] Moreover, hibernating in the "reboot" and "shutdown"
|
| D | freezing-of-tasks.txt | 123 from interfering with the suspending and resuming of devices. A user space
|
| /linux-4.4.14/net/mac80211/ |
| D | util.c | 733 if (local->quiescing || (local->suspended && !local->resuming)) { in ieee80211_can_queue_work()
1682 local->resuming = false; in ieee80211_handle_reconfig_failure()
1766 local->resuming = true; in ieee80211_reconfig()
1779 local->resuming = false; in ieee80211_reconfig()
1840 WARN_ON(local->resuming); in ieee80211_reconfig()
2071 if (!local->resuming) in ieee80211_reconfig()
2098 local->resuming = false; in ieee80211_reconfig()
2132 if (WARN_ON(!local->resuming)) in ieee80211_resume_disconnect()
|
| D | ieee80211_i.h | 1151 bool resuming; member
|
| /linux-4.4.14/drivers/usb/gadget/udc/ |
| D | dummy_hcd.c | 245 unsigned resuming:1; member
432 dum_hcd->resuming = 0; in set_link_state()
859 dum_hcd->resuming = 1; in dummy_wakeup()
1961 if (dum_hcd->resuming && time_after_eq(jiffies, dum_hcd->re_timeout)) { in dummy_hub_status()
2060 dum_hcd->resuming = 1; in dummy_hub_control()
2117 if (dum_hcd->resuming && in dummy_hub_control()
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 44 to say that its bootloader is capable of resuming. This can be as
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 104 dependent value -- if resuming execution, set it to something
200 emulation security checks, making resuming the syscall mostly
|
| /linux-4.4.14/drivers/acpi/ |
| D | ec.c | 849 static void acpi_ec_start(struct acpi_ec *ec, bool resuming) in acpi_ec_start() argument
857 if (!resuming) { in acpi_ec_start()
|
| /linux-4.4.14/Documentation/usb/ |
| D | power-management.txt | 69 However some devices have the capability of resuming by themselves, or
75 event. Examples include a suspended keyboard resuming when a key is
76 pressed, or a suspended USB hub resuming when a device is plugged in.
424 suspending and resuming correctly. This is exactly equivalent to
|
| D | persist.txt | 56 You can check the kernel log after resuming to see if either of these
|
| /linux-4.4.14/kernel/power/ |
| D | Kconfig | 70 Right now you may boot without resuming and resume later but in the
|
| /linux-4.4.14/Documentation/input/ |
| D | event-codes.txt | 186 Upon binding to a device or resuming from suspend, a driver must report
|
| /linux-4.4.14/drivers/net/ethernet/intel/igb/ |
| D | igb_main.c | 3028 static int __igb_open(struct net_device *netdev, bool resuming) in __igb_open() argument
3038 WARN_ON(resuming); in __igb_open()
3042 if (!resuming) in __igb_open()
3102 if (!resuming) in __igb_open()
3121 if (!resuming) in __igb_open()
|
| /linux-4.4.14/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 478 or pci_enable_msix_range() and resuming operation. This is not expected
|
| /linux-4.4.14/net/sched/ |
| D | Kconfig | 331 over netlink, causing the plug to be removed and resuming the normal
|
| /linux-4.4.14/drivers/platform/x86/ |
| D | Kconfig | 917 update state by resuming for a short period of time at regular
|
| /linux-4.4.14/drivers/rtc/ |
| D | Kconfig | 47 be useful to reinitialize system time when resuming from system
|
| /linux-4.4.14/drivers/scsi/ |
| D | Kconfig | 248 Note that this setting also affects whether resuming from
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 350 The S390 on initialisation & resuming of a process on a cpu sets
|
| /linux-4.4.14/Documentation/ |
| D | kernel-parameters.txt | 3636 mode before resuming the system (see
|