| /linux/drivers/pinctrl/samsung/ |
| A D | pinctrl-exynos-arm.c | 137 .resume = exynos_pinctrl_resume,
218 .resume = exynos_pinctrl_resume,
227 .resume = exynos_pinctrl_resume,
330 .resume = exynos_pinctrl_resume,
339 .resume = exynos_pinctrl_resume,
427 .resume = exynos_pinctrl_resume,
436 .resume = exynos_pinctrl_resume,
444 .resume = exynos_pinctrl_resume,
452 .resume = exynos_pinctrl_resume,
533 .resume = exynos_pinctrl_resume,
[all …]
|
| A D | pinctrl-exynos-arm64.c | 213 .resume = exynos_pinctrl_resume,
222 .resume = exynos_pinctrl_resume,
230 .resume = exynos_pinctrl_resume,
238 .resume = exynos_pinctrl_resume,
246 .resume = exynos_pinctrl_resume,
254 .resume = exynos_pinctrl_resume,
262 .resume = exynos_pinctrl_resume,
270 .resume = exynos_pinctrl_resume,
278 .resume = exynos_pinctrl_resume,
286 .resume = exynos_pinctrl_resume,
[all …]
|
| /linux/drivers/base/ |
| A D | syscore.c | 79 if (ops->resume) in syscore_suspend()
80 ops->resume(); in syscore_suspend()
100 if (ops->resume) { in syscore_resume()
101 pm_pr_dbg("Calling %pS\n", ops->resume); in syscore_resume()
102 ops->resume(); in syscore_resume()
104 "Interrupts enabled after %pS\n", ops->resume); in syscore_resume()
|
| /linux/Documentation/power/ |
| A D | swsusp.rst | 11 If you touch anything on disk between suspend and resume...
36 line or specify it using /sys/power/resume.
68 - The resume process checks for the presence of the resume device,
72 - The resume process may be triggered in two ways:
76 resume device has not been probed yet, the resume process fails and
140 resume.
304 but with resume-from-initrd, no one knows)
351 resume.
477 to resume on its own. You need an initramfs that can recognize the resume
481 echo -n "$major:$minor" > /sys/power/resume
[all …]
|
| A D | swsusp-dmcrypt.rst | 25 or an usb stick prior to resume. So you need an initrd, that sets
26 up dm-crypt and then asks swsusp to resume from the encrypted
30 a way that the swap device you suspend to/resume from has
39 resume partition, so your kernel .config contains::
67 initrd that allows you to resume from encrypted swap and that
68 continues boot with your mini system on /dev/hda1 if resume
106 echo 254:0 > /sys/power/resume
121 First we have to decide if we want to try to resume, or not.
127 device if we don't want to resume. The line "echo 254:0 > /sys/power/resume"
128 then attempts to resume from the first device mapper device.
[all …]
|
| A D | drivers-testing.rst | 2 Testing suspend and resume support in device drivers
11 resume transitions in a driver, it is necessary to suspend and resume a fully
19 resume without the driver being tested. Thus, if possible, you should first
20 resolve all suspend/resume-related problems in the test system before you start
22 for more information about the debugging of suspend/resume functionality.
27 Once you have resolved the suspend/resume-related problems with your test system
52 regarded as suspend/resume-safe.
|
| A D | s2ram.rst | 21 always it's a driver that is buggy. Thank God for the suspend/resume
25 driver that doesn't resume and recompile and reboot).
46 hash matches drivers/base/power/resume.c:28
49 which means that the last trace event was just before trying to resume
52 fix it, disable it, or trace into its resume function.
63 that "radeonfb" simply cannot resume that device - it tries to set the
65 resume it instead works fine.
71 hardware during resume operations where a value can be set that will
78 Consequence is that after a resume (even if it is successful) your system
85 quickly after the resume failure. The trace option does not use the seconds
|
| /linux/Documentation/devicetree/bindings/arm/marvell/ |
| A D | 98dx3236-resume-ctrl.txt | 7 - compatible: must be "marvell,98dx3336-resume-ctrl"
9 - reg: Should contain resume control registers location and length
13 resume@20980 {
14 compatible = "marvell,98dx3336-resume-ctrl";
|
| /linux/drivers/net/phy/ |
| A D | intel-xway.c | 361 .resume = genphy_resume,
372 .resume = genphy_resume,
383 .resume = genphy_resume,
394 .resume = genphy_resume,
404 .resume = genphy_resume,
414 .resume = genphy_resume,
424 .resume = genphy_resume,
434 .resume = genphy_resume,
444 .resume = genphy_resume,
454 .resume = genphy_resume,
|
| A D | realtek.c | 856 .resume = genphy_resume,
865 .resume = genphy_resume,
901 .resume = genphy_resume,
911 .resume = genphy_resume,
923 .resume = rtl821x_resume,
931 .resume = rtlgen_resume,
943 .resume = rtlgen_resume,
955 .resume = rtlgen_resume,
1012 .resume = genphy_resume,
1023 .resume = genphy_resume,
[all …]
|
| A D | mxl-gpy.c | 523 .resume = genphy_resume,
541 .resume = genphy_resume,
558 .resume = genphy_resume,
576 .resume = genphy_resume,
593 .resume = genphy_resume,
611 .resume = genphy_resume,
628 .resume = genphy_resume,
646 .resume = genphy_resume,
663 .resume = genphy_resume,
680 .resume = genphy_resume,
[all …]
|
| A D | smsc.c | 358 .resume = genphy_resume,
382 .resume = genphy_resume,
411 .resume = genphy_resume,
429 .resume = genphy_resume,
459 .resume = genphy_resume,
485 .resume = genphy_resume,
|
| A D | micrel.c | 1634 .resume = genphy_resume,
1649 .resume = genphy_resume,
1664 .resume = genphy_resume,
1696 .resume = genphy_resume,
1710 .resume = genphy_resume,
1725 .resume = genphy_resume,
1744 .resume = kszphy_resume,
1756 .resume = genphy_resume,
1772 .resume = genphy_resume,
1791 .resume = kszphy_resume,
[all …]
|
| /linux/Documentation/devicetree/bindings/arm/cpu-enable-method/ |
| A D | al,alpine-smp | 17 "al,alpine-cpu-resume" and "al,alpine-nb-service".
20 * Alpine CPU resume registers
22 The CPU resume register are used to define required resume address after
26 - compatible : Should contain "al,alpine-cpu-resume".
73 compatible = "al,alpine-cpu-resume";
|
| /linux/drivers/pnp/ |
| A D | driver.c | 220 if (pnp_dev->protocol->resume) { in pnp_bus_resume()
221 error = pnp_dev->protocol->resume(pnp_dev); in pnp_bus_resume()
232 if (pnp_drv->driver.pm && pnp_drv->driver.pm->resume) { in pnp_bus_resume()
233 error = pnp_drv->driver.pm->resume(dev); in pnp_bus_resume()
238 if (pnp_drv->resume) { in pnp_bus_resume()
239 error = pnp_drv->resume(pnp_dev); in pnp_bus_resume()
250 .resume = pnp_bus_resume,
|
| /linux/Documentation/admin-guide/pm/ |
| A D | suspend-flows.rst | 23 working state is referred to as *system resume*.
25 The kernel code flows associated with the suspend and resume transitions for
34 resume hooks that need to be provided by the platform driver to make them
93 deferred till the subsequent system resume transition as described
115 system wakeup, in which case the system resume transition is started.
135 the system resume transition begins.
139 Devices are resumed in four phases called *noirq resume*, *early resume*,
140 *resume* and *complete* (see :ref:`driverapi_pm_devices` for more
148 supports it during the *early* resume phase.
157 4. Invoking system-wide resume notifiers.
[all …]
|
| /linux/Documentation/arm/samsung-s3c24xx/ |
| A D | suspend.rst | 18 1) A bootloader that can support the necessary resume operation
20 2) Support for at least 1 source for resume
25 time require suspend/resume support.
34 code to resume Linux operation.
54 saving the resume address, if your board requires it, then contact
95 3) If any debugging is placed in the resume path, then it must have the
106 aspects of how the S3C2410 suspend and resume support is configured
|
| /linux/Documentation/watchdog/ |
| A D | watchdog-pm.rst | 15 Ping on resume
17 On resume, a watchdog timer shall be reset to its selected value to give
18 userspace enough time to resume. [1] [2]
|
| /linux/Documentation/driver-api/pm/ |
| A D | notifiers.rst | 14 before hibernation/suspend or after restore/resume, but they require the system
16 ``->resume()`` or even ``->prepare()`` and ``->complete()`` callbacks are not
20 resume/restore, but they cannot do it by calling :c:func:`request_firmware()`
21 from their ``->resume()`` or ``->complete()`` callback routines (user land
24 ``->resume()`` routine. A suspend/hibernation notifier may be used for that.
54 resume callbacks have been executed and tasks have been thawed.
|
| /linux/arch/arm/include/asm/ |
| A D | outercache.h | 25 void (*resume)(void); member
102 if (outer_cache.resume) in outer_resume()
103 outer_cache.resume(); in outer_resume()
|
| /linux/kernel/power/ |
| A D | Kconfig | 96 string "Default resume partition"
109 resume=/dev/<other device>
111 which will set the resume partition to the device specified.
194 bool "Test suspend/resume and wakealarm during bootup"
209 bool "Device suspend/resume watchdog"
213 locked up attempting to suspend/resume a device.
232 functions from <linux/resume-trace.h> as well as the
233 <asm/resume-trace.h> header with a TRACE_RESUME() macro.
240 bool "Suspend/resume event tracing"
247 during suspend (or more commonly, during resume).
[all …]
|
| /linux/drivers/xen/events/ |
| A D | events_internal.h | 28 void (*resume)(void); member
104 if (evtchn_ops->resume) in xen_evtchn_resume()
105 evtchn_ops->resume(); in xen_evtchn_resume()
|
| /linux/Documentation/driver-api/firmware/ |
| A D | firmware_cache.rst | 6 re-initialize devices. During resume there may be a period of time during which
15 driver's suspend and resume callback. Users of these API calls needn't cache
16 the firmware by themselves for dealing with firmware loss during system resume.
19 caching it in memory. Upon resume device drivers using the firmware API will
41 will still be used on resume from suspend.
|
| /linux/drivers/gpu/drm/gma500/ |
| A D | gtt.c | 75 int resume) in psb_gtt_insert() argument
92 if (!resume) { in psb_gtt_insert()
348 int psb_gtt_init(struct drm_device *dev, int resume) in psb_gtt_init() argument
361 if (!resume) { in psb_gtt_init()
434 if (resume && (gtt_pages != pg->gtt_pages) && in psb_gtt_init()
448 if (!resume) in psb_gtt_init()
457 if (!resume) in psb_gtt_init()
|
| /linux/arch/arm/mach-s3c/ |
| A D | pm-gpio.c | 61 .resume = samsung_gpio_pm_1bit_resume,
188 .resume = samsung_gpio_pm_2bit_resume,
299 .resume = samsung_gpio_pm_4bit_resume,
357 if (pm == NULL || pm->resume == NULL) in samsung_pm_resume_gpio()
360 pm->resume(ourchip); in samsung_pm_resume_gpio()
|