| /Linux-v4.19/Documentation/power/ |
| D | basic-pm-debugging.txt | 1 Debugging hibernation and suspend
4 1. Testing hibernation (aka suspend to disk or STD)
6 To check if hibernation works, you can try to hibernate in the "reboot" mode:
11 and the system should create a hibernation image, reboot, resume and get back to
13 hibernation is most likely to work correctly. Still, you need to repeat the
18 systems might be necessary to make hibernation work. Thus, if your machine fails
24 which is the default and recommended mode of hibernation.
26 Unfortunately, the "platform" mode of hibernation does not work on some systems
27 with broken BIOSes. In such cases the "shutdown" mode of hibernation might
36 If neither "platform" nor "shutdown" hibernation mode works, you will need to
[all …]
|
| D | interface.txt | 20 too as long the kernel has been configured to support hibernation at all
30 /sys/power/disk controls the operating mode of hibernation (Suspend-to-Disk).
31 Specifically, it tells the kernel what to do after creating a hibernation image.
39 'test_resume' (resume-after-hibernation test mode)
44 mechanism to put the system to sleep after creating a hibernation image (ACPI
51 /sys/power/image_size controls the size of hibernation images.
54 used as a best-effort upper limit of the image size, in bytes. The hibernation
56 However, if that turns out to be impossible to achieve, a hibernation image will
58 writing '0' to this file will enforce hibernation images to be as small as
|
| D | freezing-of-tasks.txt | 7 kernel threads are controlled during hibernation or system-wide suspend (on some
16 suspend state as well as before a hibernation image is created (in what follows
17 we only consider hibernation, but the description also applies to suspend).
19 Namely, as the first step of the hibernation procedure the function
58 hibernation operation will be cancelled. For this reason, freezable kernel
62 After the system memory state has been restored from a hibernation image and
100 hibernation. At the moment we have no simple means of checkpointing
103 modifications. At the same time each hibernation image contains some
109 hibernation image has been created and before the system is finally powered off.
113 2. Next, to create the hibernation image we need to free a sufficient amount of
[all …]
|
| D | drivers-testing.txt | 9 several times, preferably several times in a row, and separately for hibernation
25 a) Build the driver as a module, load it and try the test modes of hibernation
32 hibernation.
|
| D | pci.txt | 543 System hibernation is more complicated than system suspend, because it requires
622 System restore requires a hibernation image to be loaded into memory and the
623 pre-hibernation memory contents to be restored before the pre-hibernation system
626 As described in Documentation/driver-api/pm/devices.rst, the hibernation image is loaded
632 the image during hibernation, in the
640 Should the restoration of the pre-hibernation memory contents fail, the boot
645 If the pre-hibernation memory contents are restored successfully, which is the
648 it must restore the devices' pre-hibernation functionality, which is done much
702 The prepare() callback is executed during system suspend, during hibernation
703 (when a hibernation image is about to be created), during power-off after
[all …]
|
| D | userland-swsusp.txt | 61 SNAPSHOT_GET_IMAGE_SIZE - return the actual size of the hibernation image
83 SNAPSHOT_PLATFORM_SUPPORT - enable/disable the hibernation platform support,
86 SNAPSHOT_POWER_OFF - make the kernel transition the system to the hibernation
|
| D | swsusp.txt | 44 . If you would like to write hibernation image to swap and then suspend
62 if found, it then checks the contents for the hibernation image signature.
63 If both are found, it resumes the hibernation image.
96 parameter, it saves hibernation image without compression.
173 kernel threads are controlled during hibernation or system-wide suspend (on some
|
| D | runtime_pm.txt | 16 hibernation and resume from system sleep states). pm_wq is declared in
612 Runtime PM and system sleep (i.e., system suspend and hibernation, also known
638 physical state. This can happen during resume from hibernation.
669 place (in particular, if the system is not waking up from hibernation), it may
682 related to hibernation (see Documentation/driver-api/pm/devices.rst for more
686 the runtime PM and system suspend/resume (and hibernation) callbacks by carrying
|
| D | suspend-and-cpuhotplug.txt | 226 However, in the case of hibernation, since all the CPUs are completely
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-driver-intel-rapid-start | 6 1: Wake to enter hibernation when the wakeup timer expires
7 2: Wake to enter hibernation when the battery reaches a
11 indicates that the system will wake to enter hibernation when
20 remain asleep before waking up to enter hibernation.
|
| D | sysfs-devices-power | 16 RAM) and hibernation (suspend to disk), and to enable or disable
62 transitions (eg. suspend to RAM, hibernation).
222 hibernation.
247 devices and on system-wide suspend/resume and hibernation.
262 hibernation.
|
| D | sysfs-power | 16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
187 drivers during the "device freeze" stage of hibernation. It can
299 the kernel will be using on the next hibernation
|
| /Linux-v4.19/Documentation/driver-api/pm/ |
| D | notifiers.rst | 10 before hibernation/suspend or after restore/resume, but they require the system
20 ``->resume()`` routine. A suspend/hibernation notifier may be used for that.
32 The system memory state has been restored from a hibernation image or an
33 error occurred during hibernation. Device restore callbacks have been
37 The system is going to restore a hibernation image. If all goes well,
42 An error occurred during restore from hibernation. Device restore
62 The hibernation and suspend notifiers are called with :c:data:`pm_mutex` held.
|
| D | devices.rst | 40 (mostly for systems with disks) "hibernation" (also known as
65 transitions (suspend or hibernation).
273 sleep states and the hibernation state ("suspend-to-disk"). Each phase involves
509 more phases for hibernation, with a different set of callbacks. These phases
512 The general procedure for hibernation is to quiesce all devices ("freeze"),
581 Resuming from hibernation is, again, more complicated than resuming from a sleep
583 a system image to be loaded into memory and the pre-hibernation memory contents
587 pre-hibernation memory contents restored by the boot loader, in practice this
592 reads the system image, restores the pre-hibernation memory contents, and passes
594 in resuming from hibernation. In fact, the restore kernel may be completely
[all …]
|
| /Linux-v4.19/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 19 hibernation and up to three variants of system suspend. The sleep states that
114 It takes three system state changes to put it into hibernation and two system
117 First, when hibernation is triggered, the kernel stops all system activity and
135 (referred to as the ``restore kernel``) looks for a hibernation image in
141 image kernel restores the system to the pre-hibernation state and allows user
162 :ref:`hibernation <hibernation>`, :ref:`suspend-to-idle <s2idle>` and
191 that can be carried out after the hibernation image has been saved. The
210 the hibernation image and continue. Otherwise, use the image
215 just woken up from hibernation and the currently running kernel
224 and saving the image next time hibernation is triggered by writing
[all …]
|
| /Linux-v4.19/drivers/usb/dwc2/ |
| D | core_intr.c | 492 hsotg->hw_params.hibernation); in dwc2_handle_usb_suspend_intr()
518 if (hsotg->hw_params.hibernation) { in dwc2_handle_usb_suspend_intr()
725 if (hsotg->hw_params.hibernation && in dwc2_handle_gpwrdn_intr()
743 if (hsotg->hw_params.hibernation && in dwc2_handle_gpwrdn_intr()
|
| D | params.c | 256 if (hsotg->hw_params.hibernation) in dwc2_set_param_power_down()
504 if (hsotg->hw_params.hibernation) in dwc2_check_param_power_down()
778 hw->hibernation = !!(hwcfg4 & GHWCFG4_HIBER); in dwc2_get_hwparams()
|
| D | core.h | 634 unsigned hibernation:1; member
|
| /Linux-v4.19/mm/ |
| D | Kconfig.debug | 24 this option cannot be enabled in combination with hibernation as
|
| /Linux-v4.19/Documentation/ |
| D | rfkill.txt | 76 suspend/hibernation, in which case it will be necessary to update the rfkill
|
| /Linux-v4.19/drivers/gpu/drm/i915/ |
| D | i915_drv.c | 1613 static int i915_drm_suspend_late(struct drm_device *dev, bool hibernation) in i915_drm_suspend_late() argument
1633 if (IS_GEN9_LP(dev_priv) || hibernation || !suspend_to_idle(dev_priv) || in i915_drm_suspend_late()
1670 if (!(hibernation && INTEL_GEN(dev_priv) < 6)) in i915_drm_suspend_late()
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | kernel-parameters.rst | 153 SWSUSP Software suspend (hibernation) is enabled.
|
| /Linux-v4.19/Documentation/driver-api/usb/ |
| D | persist.rst | 58 available during hibernation (also known as swsusp or suspend-to-disk).
|
| D | power-management.rst | 325 waking up from hibernation, as many systems do not maintain suspend
326 current to the USB host controllers during hibernation. (It's
327 possible to work around the hibernation-forces-disconnect problem by
|
| /Linux-v4.19/kernel/power/ |
| D | Kconfig | 43 called "hibernation" in user interfaces. STD checkpoints the
|
