| /Linux-v4.19/drivers/pinctrl/samsung/ |
| D | pinctrl-exynos-arm.c | 136 .resume = exynos_pinctrl_resume,
217 .resume = exynos_pinctrl_resume,
226 .resume = exynos_pinctrl_resume,
329 .resume = exynos_pinctrl_resume,
338 .resume = exynos_pinctrl_resume,
426 .resume = exynos_pinctrl_resume,
435 .resume = exynos_pinctrl_resume,
443 .resume = exynos_pinctrl_resume,
451 .resume = exynos_pinctrl_resume,
532 .resume = exynos_pinctrl_resume,
[all …]
|
| D | pinctrl-exynos-arm64.c | 195 .resume = exynos_pinctrl_resume,
204 .resume = exynos_pinctrl_resume,
212 .resume = exynos_pinctrl_resume,
220 .resume = exynos_pinctrl_resume,
228 .resume = exynos_pinctrl_resume,
236 .resume = exynos_pinctrl_resume,
244 .resume = exynos_pinctrl_resume,
252 .resume = exynos_pinctrl_resume,
260 .resume = exynos_pinctrl_resume,
268 .resume = exynos_pinctrl_resume,
|
| /Linux-v4.19/drivers/base/ |
| D | syscore.c | 80 if (ops->resume) in syscore_suspend()
81 ops->resume(); in syscore_suspend()
101 if (ops->resume) { in syscore_resume()
103 pr_info("PM: Calling %pF\n", ops->resume); in syscore_resume()
104 ops->resume(); in syscore_resume()
106 "Interrupts enabled after %pF\n", ops->resume); in syscore_resume()
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/marvell/ |
| 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-v4.19/drivers/net/phy/ |
| D | intel-xway.c | 252 .resume = genphy_resume,
265 .resume = genphy_resume,
278 .resume = genphy_resume,
291 .resume = genphy_resume,
303 .resume = genphy_resume,
315 .resume = genphy_resume,
327 .resume = genphy_resume,
339 .resume = genphy_resume,
351 .resume = genphy_resume,
363 .resume = genphy_resume,
|
| D | realtek.c | 230 .resume = genphy_resume,
252 .resume = rtl8211b_resume,
270 .resume = genphy_resume,
280 .resume = genphy_resume,
291 .resume = genphy_resume,
302 .resume = genphy_resume,
|
| D | smsc.c | 235 .resume = genphy_resume,
260 .resume = genphy_resume,
286 .resume = genphy_resume,
305 .resume = genphy_resume,
331 .resume = genphy_resume,
357 .resume = genphy_resume,
|
| D | micrel.c | 817 .resume = genphy_resume,
833 .resume = genphy_resume,
849 .resume = genphy_resume,
866 .resume = genphy_resume,
882 .resume = genphy_resume,
898 .resume = genphy_resume,
914 .resume = genphy_resume,
930 .resume = kszphy_resume,
941 .resume = genphy_resume,
957 .resume = genphy_resume,
[all …]
|
| /Linux-v4.19/Documentation/power/ |
| D | drivers-testing.txt | 1 Testing suspend and resume support in device drivers
7 resume transitions in a driver, it is necessary to suspend and resume a fully
15 resume without the driver being tested. Thus, if possible, you should first
16 resolve all suspend/resume-related problems in the test system before you start
18 for more information about the debugging of suspend/resume functionality.
22 Once you have resolved the suspend/resume-related problems with your test system
46 regarded as suspend/resume-safe.
|
| D | swsusp-dmcrypt.txt | 23 or an usb stick prior to resume. So you need an initrd, that sets
24 up dm-crypt and then asks swsusp to resume from the encrypted
28 a way that the swap device you suspend to/resume from has
37 resume partition, so your kernel .config contains:
65 initrd that allows you to resume from encrypted swap and that
66 continues boot with your mini system on /dev/hda1 if resume
104 echo 254:0 > /sys/power/resume
119 First we have to decide if we want to try to resume, or not.
120 We will not resume if booting with "noresume" or any parameters
125 device if we don't want to resume. The line "echo 254:0 > /sys/power/resume"
[all …]
|
| D | swsusp.txt | 5 * If you touch anything on disk between suspend and resume...
8 * If you do resume from initrd after your filesystems are mounted...
15 * between suspend and resume, it may do something wrong. If you change
19 * (*) suspend/resume support is needed to make it safe.
22 * they won't be accessible after resume and you may lose data, as though
28 You need to append resume=/dev/your_swap_partition to kernel command
29 line or specify it using /sys/power/resume.
32 If using a swapfile you can also specify a resume offset using
50 support. For suspend and resume to work, make sure your disk drivers
52 suspend/resume with modular disk drivers, see FAQ, but you probably
[all …]
|
| D | s2ram.txt | 19 always it's a driver that is buggy. Thank God for the suspend/resume
23 driver that doesn't resume and recompile and reboot).
44 hash matches drivers/base/power/resume.c:28
47 which means that the last trace event was just before trying to resume
50 fix it, disable it, or trace into its resume function.
61 that "radeonfb" simply cannot resume that device - it tries to set the
63 resume it instead works fine.
69 hardware during resume operations where a value can be set that will
76 Consequence is that after a resume (even if it is successful) your system
83 quickly after the resume failure. The trace option does not use the seconds
|
| /Linux-v4.19/sound/soc/uniphier/ |
| D | aio-ld11.c | 222 .resume = uniphier_aio_dai_resume,
246 .resume = uniphier_aio_dai_resume,
261 .resume = uniphier_aio_dai_resume,
283 .resume = uniphier_aio_dai_resume,
298 .resume = uniphier_aio_dai_resume,
313 .resume = uniphier_aio_dai_resume,
328 .resume = uniphier_aio_dai_resume,
345 .resume = uniphier_aio_dai_resume,
362 .resume = uniphier_aio_dai_resume,
|
| D | aio-pxs2.c | 175 .resume = uniphier_aio_dai_resume,
190 .resume = uniphier_aio_dai_resume,
212 .resume = uniphier_aio_dai_resume,
234 .resume = uniphier_aio_dai_resume,
249 .resume = uniphier_aio_dai_resume,
264 .resume = uniphier_aio_dai_resume,
278 .resume = uniphier_aio_dai_resume,
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/ |
| D | al,alpine.txt | 56 * Alpine CPU resume registers
58 The CPU resume register are used to define required resume address after
62 - compatible : Should contain "al,alpine-cpu-resume".
68 compatible = "al,alpine-cpu-resume";
|
| /Linux-v4.19/drivers/pnp/ |
| D | driver.c | 219 if (pnp_dev->protocol->resume) { in pnp_bus_resume()
220 error = pnp_dev->protocol->resume(pnp_dev); in pnp_bus_resume()
231 if (pnp_drv->driver.pm && pnp_drv->driver.pm->resume) { in pnp_bus_resume()
232 error = pnp_drv->driver.pm->resume(dev); in pnp_bus_resume()
237 if (pnp_drv->resume) { in pnp_bus_resume()
238 error = pnp_drv->resume(pnp_dev); in pnp_bus_resume()
249 .resume = pnp_bus_resume,
|
| /Linux-v4.19/arch/arm/include/asm/ |
| D | outercache.h | 37 void (*resume)(void); member
114 if (outer_cache.resume) in outer_resume()
115 outer_cache.resume(); in outer_resume()
|
| /Linux-v4.19/include/linux/clk/ |
| D | tegra.h | 52 void (*resume)(void); member
117 if (WARN_ON(!tegra_cpu_car_ops->resume)) in tegra_cpu_clock_resume()
120 tegra_cpu_car_ops->resume(); in tegra_cpu_clock_resume()
|
| /Linux-v4.19/Documentation/driver-api/pm/ |
| D | notifiers.rst | 10 before hibernation/suspend or after restore/resume, but they require the system
12 ``->resume()`` or even ``->prepare()`` and ``->complete()`` callbacks are not
16 resume/restore, but they cannot do it by calling :c:func:`request_firmware()`
17 from their ``->resume()`` or ``->complete()`` callback routines (user land
20 ``->resume()`` routine. A suspend/hibernation notifier may be used for that.
50 resume callbacks have been executed and tasks have been thawed.
|
| /Linux-v4.19/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 17 1) A bootloader that can support the necessary resume operation
19 2) Support for at least 1 source for resume
24 time require suspend/resume support.
33 code to resume Linux operation.
53 saving the resume address, if your board requires it, then contact
94 3) If any debugging is placed in the resume path, then it must have the
105 aspects of how the S3C2410 suspend and resume support is configured
|
| /Linux-v4.19/kernel/power/ |
| D | Kconfig | 47 after placing resume=/dev/swappartition on the kernel command line
60 boot, pass the 'resume=/dev/swappartition' argument to the kernel to
70 Right now you may boot without resuming and resume later but in the
83 string "Default resume partition"
87 The default resume partition is the partition that the suspend-
96 resume=/dev/<other device>
98 which will set the resume partition to the device specified.
174 bool "Test suspend/resume and wakealarm during bootup"
189 bool "Device suspend/resume watchdog"
193 locked up attempting to suspend/resume a device.
[all …]
|
| /Linux-v4.19/drivers/xen/events/ |
| D | events_internal.h | 73 void (*resume)(void); member
144 if (evtchn_ops->resume) in xen_evtchn_resume()
145 evtchn_ops->resume(); in xen_evtchn_resume()
|
| /Linux-v4.19/Documentation/driver-api/firmware/ |
| 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-v4.19/arch/x86/include/asm/ |
| D | tsc.h | 59 extern void tsc_verify_tsc_adjust(bool resume);
64 static inline void tsc_verify_tsc_adjust(bool resume) { } in tsc_verify_tsc_adjust() argument
|
| /Linux-v4.19/arch/arm/plat-samsung/ |
| 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()
|
