| /Linux-v5.4/Documentation/power/ |
| D | basic-pm-debugging.rst | 2 Debugging hibernation and suspend
7 1. Testing hibernation (aka suspend to disk or STD)
10 To check if hibernation works, you can try to hibernate in the "reboot" mode::
15 and the system should create a hibernation image, reboot, resume and get back to
17 hibernation is most likely to work correctly. Still, you need to repeat the
22 systems might be necessary to make hibernation work. Thus, if your machine
29 which is the default and recommended mode of hibernation.
31 Unfortunately, the "platform" mode of hibernation does not work on some systems
32 with broken BIOSes. In such cases the "shutdown" mode of hibernation might
41 If neither "platform" nor "shutdown" hibernation mode works, you will need to
[all …]
|
| D | interface.rst | 22 too as long the kernel has been configured to support hibernation at all
32 /sys/power/disk controls the operating mode of hibernation (Suspend-to-Disk).
33 Specifically, it tells the kernel what to do after creating a hibernation image.
41 - 'test_resume' (resume-after-hibernation test mode)
46 mechanism to put the system to sleep after creating a hibernation image (ACPI
53 /sys/power/image_size controls the size of hibernation images.
56 used as a best-effort upper limit of the image size, in bytes. The hibernation
58 However, if that turns out to be impossible to achieve, a hibernation image will
60 writing '0' to this file will enforce hibernation images to be as small as
|
| D | freezing-of-tasks.rst | 11 kernel threads are controlled during hibernation or system-wide suspend (on some
21 suspend state as well as before a hibernation image is created (in what follows
22 we only consider hibernation, but the description also applies to suspend).
24 Namely, as the first step of the hibernation procedure the function
63 hibernation operation will be cancelled. For this reason, freezable kernel
67 After the system memory state has been restored from a hibernation image and
107 hibernation. At the moment we have no simple means of checkpointing
110 modifications. At the same time each hibernation image contains some
116 modified after the hibernation image has been created and before the
121 2. Next, to create the hibernation image we need to free a sufficient amount of
[all …]
|
| D | drivers-testing.rst | 13 several times, preferably several times in a row, and separately for hibernation
30 a) Build the driver as a module, load it and try the test modes of hibernation
37 hibernation.
|
| D | pci.rst | 555 System hibernation is more complicated than system suspend, because it requires
635 System restore requires a hibernation image to be loaded into memory and the
636 pre-hibernation memory contents to be restored before the pre-hibernation system
639 As described in Documentation/driver-api/pm/devices.rst, the hibernation image is loaded
645 the image during hibernation, in the
653 Should the restoration of the pre-hibernation memory contents fail, the boot
658 If the pre-hibernation memory contents are restored successfully, which is the
661 it must restore the devices' pre-hibernation functionality, which is done much
717 The prepare() callback is executed during system suspend, during hibernation
718 (when a hibernation image is about to be created), during power-off after
[all …]
|
| D | userland-swsusp.rst | 71 return the actual size of the hibernation image
98 enable/disable the hibernation platform support,
102 make the kernel transition the system to the hibernation
|
| D | swsusp.rst | 51 - If you would like to write hibernation image to swap and then suspend
69 if found, it then checks the contents for the hibernation image signature.
70 If both are found, it resumes the hibernation image.
106 parameter, it saves hibernation image without compression.
195 kernel threads are controlled during hibernation or system-wide suspend (on some
|
| D | runtime_pm.rst | 21 hibernation and resume from system sleep states). pm_wq is declared in
622 Runtime PM and system sleep (i.e., system suspend and hibernation, also known
648 physical state. This can happen during resume from hibernation.
679 place (in particular, if the system is not waking up from hibernation), it may
692 related to hibernation (see Documentation/driver-api/pm/devices.rst for more
696 the runtime PM and system suspend/resume (and hibernation) callbacks by carrying
|
| D | suspend-and-cpuhotplug.rst | 235 However, in the case of hibernation, since all the CPUs are completely
|
| /Linux-v5.4/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-v5.4/Documentation/driver-api/pm/ |
| D | notifiers.rst | 14 before hibernation/suspend or after restore/resume, but they require the system
24 ``->resume()`` routine. A suspend/hibernation notifier may be used for that.
36 The system memory state has been restored from a hibernation image or an
37 error occurred during hibernation. Device restore callbacks have been
41 The system is going to restore a hibernation image. If all goes well,
46 An error occurred during restore from hibernation. Device restore
66 The hibernation and suspend notifiers are called with :c:data:`pm_mutex` held.
|
| D | devices.rst | 46 (mostly for systems with disks) "hibernation" (also known as
71 transitions (suspend or hibernation).
279 sleep states and the hibernation state ("suspend-to-disk"). Each phase involves
515 more phases for hibernation, with a different set of callbacks. These phases
518 The general procedure for hibernation is to quiesce all devices ("freeze"),
587 Resuming from hibernation is, again, more complicated than resuming from a sleep
589 a system image to be loaded into memory and the pre-hibernation memory contents
593 pre-hibernation memory contents restored by the boot loader, in practice this
598 reads the system image, restores the pre-hibernation memory contents, and passes
600 in resuming from hibernation. In fact, the restore kernel may be completely
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 23 hibernation and up to three variants of system suspend. The sleep states that
118 It takes three system state changes to put it into hibernation and two system
121 First, when hibernation is triggered, the kernel stops all system activity and
139 (referred to as the ``restore kernel``) looks for a hibernation image in
145 image kernel restores the system to the pre-hibernation state and allows user
166 :ref:`hibernation <hibernation>`, :ref:`suspend-to-idle <s2idle>` and
195 that can be carried out after the hibernation image has been saved. The
214 the hibernation image and continue. Otherwise, use the image
219 just woken up from hibernation and the currently running kernel
228 and saving the image next time hibernation is triggered by writing
[all …]
|
| /Linux-v5.4/drivers/usb/dwc2/ |
| D | core_intr.c | 504 hsotg->hw_params.hibernation); in dwc2_handle_usb_suspend_intr()
530 if (hsotg->hw_params.hibernation) { in dwc2_handle_usb_suspend_intr()
737 if (hsotg->hw_params.hibernation && in dwc2_handle_gpwrdn_intr()
755 if (hsotg->hw_params.hibernation && in dwc2_handle_gpwrdn_intr()
|
| D | params.c | 288 if (hsotg->hw_params.hibernation) in dwc2_set_param_power_down()
549 if (hsotg->hw_params.hibernation) in dwc2_check_param_power_down()
824 hw->hibernation = !!(hwcfg4 & GHWCFG4_HIBER); in dwc2_get_hwparams()
|
| D | core.h | 660 unsigned hibernation:1; member
|
| /Linux-v5.4/mm/ |
| D | Kconfig.debug | 31 be enabled in combination with hibernation as that would result in
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | rfkill.rst | 76 suspend/hibernation, in which case it will be necessary to update the rfkill
|
| /Linux-v5.4/drivers/gpu/drm/i915/ |
| D | i915_drv.c | 1839 static int i915_drm_suspend_late(struct drm_device *dev, bool hibernation) in i915_drm_suspend_late() argument
1855 get_suspend_mode(dev_priv, hibernation)); in i915_drm_suspend_late()
1882 if (!(hibernation && INTEL_GEN(dev_priv) < 6)) in i915_drm_suspend_late()
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | kernel-parameters.rst | 154 SWSUSP Software suspend (hibernation) is enabled.
|
| /Linux-v5.4/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-v5.4/kernel/power/ |
| D | Kconfig | 44 called "hibernation" in user interfaces. STD checkpoints the
|
