| /linux/drivers/pinctrl/samsung/ |
| H A D | pinctrl-exynos-arm.c | 151 .resume = exynos_pinctrl_resume,
232 .resume = exynos_pinctrl_resume,
241 .resume = exynos_pinctrl_resume,
344 .resume = exynos_pinctrl_resume,
353 .resume = exynos_pinctrl_resume,
441 .resume = exynos_pinctrl_resume,
450 .resume = exynos_pinctrl_resume,
458 .resume = exynos_pinctrl_resume,
466 .resume = exynos_pinctrl_resume,
547 .resume = exynos_pinctrl_resume,
[all …]
|
| /linux/drivers/base/ |
| H A D | syscore.c | 81 if (syscore->ops->resume) in syscore_suspend()
82 syscore->ops->resume(syscore->data); in syscore_suspend()
102 if (syscore->ops->resume) { in syscore_resume()
103 pm_pr_dbg("Calling %pS\n", syscore->ops->resume); in syscore_resume()
104 syscore->ops->resume(syscore->data); in syscore_resume()
107 syscore->ops->resume); in syscore_resume()
|
| /linux/Documentation/devicetree/bindings/arm/cpu-enable-method/ |
| H 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".
63 compatible = "al,alpine-cpu-resume";
|
| /linux/Documentation/power/ |
| H A D | swsusp.rst | 11 If you touch anything on disk between suspend and resume...
14 If you do resume from initrd after your filesystems are mounted...
22 between suspend and resume, it may do something wrong. If you change
26 ( ) suspend/resume support is needed to make it safe.
29 they won't be accessible after resume and you may lose data, as though
35 You need to append resume=/dev/your_swap_partition to kernel command
36 line or specify it using /sys/power/resume.
39 If using a swapfile you can also specify a resume offset using
57 support. For suspend and resume to work, make sure your disk drivers
59 suspend/resume with modular disk drivers, see FAQ, but you probably
[all …]
|
| H 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.
122 We will not resume if booting with "noresume" or any parameters
127 device if we don't want to resume. The line "echo 254:0 > /sys/power/resume"
[all …]
|
| H 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.
|
| H 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
|
| H A D | video.rst | 2 Video issues with S3 resume
7 During S3 resume, hardware needs to be reinitialized. For most
14 This is not problem for swsusp, because during swsusp resume, BIOS is
19 We either have to run video BIOS during early resume, or interpret it
34 so it makes debugging of early resume problems
40 There are a few types of systems where video works after S3 resume:
45 resume. Unfortunately, it is not correct to call the video BIOS at
78 bios, you'll get a hard crash during resume. Be careful. Also it is
81 resume.
158 IBM TP T41p s3_bios (2), switch to X after resume
|
| /linux/Documentation/devicetree/bindings/arm/marvell/ |
| H 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/Documentation/admin-guide/pm/ |
| H 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
35 available. Apart from that, the suspend and resume code flows for these sleep
51 transition is about to occur and when the resume transition has finished.
65 put into uninterruptible sleep until the end of the subsequent system resume
74 resume, which can be much more precise than the freezing, so the latter is
93 deferred till the subsequent system resume transition as described
96 IRQs associated with system wakeup devices are "armed" so that the resume
115 system wakeup, in which case the system resume transition is started.
[all …]
|
| /linux/drivers/pnp/ |
| H A D | driver.c | 239 if (pnp_dev->protocol->resume) { in pnp_bus_resume()
240 error = pnp_dev->protocol->resume(pnp_dev); in pnp_bus_resume()
251 if (pnp_drv->driver.pm && pnp_drv->driver.pm->resume) { in pnp_bus_resume()
252 error = pnp_drv->driver.pm->resume(dev); in pnp_bus_resume()
257 if (pnp_drv->resume) { in pnp_bus_resume()
258 error = pnp_drv->resume(pnp_dev); in pnp_bus_resume()
269 .resume = pnp_bus_resume,
|
| /linux/Documentation/watchdog/ |
| H 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/arch/arm/include/asm/ |
| H 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/Documentation/driver-api/pm/ |
| H 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/drivers/net/phy/ |
| H A D | intel-xway.c | 546 .resume = genphy_resume,
562 .resume = genphy_resume,
578 .resume = genphy_resume,
594 .resume = genphy_resume,
609 .resume = genphy_resume,
624 .resume = genphy_resume,
639 .resume = genphy_resume,
654 .resume = genphy_resume,
669 .resume = genphy_resume,
684 .resume = genphy_resume,
|
| /linux/Documentation/trace/coresight/ |
| H A D | coresight-perf.rst | 81 Fine-grained tracing with AUX pause and resume
87 provides AUX pause and resume functionality for fine-grained tracing.
89 The AUX pause and resume can be triggered by associated events. These
92 session with AUX pause / resume, three configuration terms are
99 - "aux-action=resume": an associated event is specified with this term
100 to resume AUX trace.
102 Example for triggering AUX pause and resume with ftrace tracepoints::
104 …perf record -e cs_etm/aux-action=start-paused/k,syscalls:sys_enter_openat/aux-action=resume/,sysca…
106 Example for triggering AUX pause and resume with PMU event::
110 -e cycles/aux-action=resume,period=1050000/ -- sleep 1
|
| /linux/drivers/xen/events/ |
| H A D | events_internal.h | 28 void (*resume)(void); member
103 if (evtchn_ops->resume) in xen_evtchn_resume()
104 evtchn_ops->resume(); in xen_evtchn_resume()
|
| /linux/Documentation/driver-api/firmware/ |
| H 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/arch/arm/mach-s3c/ |
| H 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()
|
| /linux/drivers/net/phy/realtek/ |
| H A D | realtek_main.c | 2154 .resume = genphy_resume,
2163 .resume = genphy_resume,
2182 .resume = rtl8211b_resume,
2199 .resume = genphy_resume,
2209 .resume = genphy_resume,
2226 .resume = rtl8211f_resume,
2242 .resume = rtl821x_resume,
2251 .resume = rtlgen_resume,
2263 .resume = rtlgen_resume,
2279 .resume = rtlgen_resume,
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| H A D | power-management.rst | 69 When a device has been suspended, it generally doesn't resume until
71 suspended, it generally doesn't resume until the user tells it to, say
75 asking the kernel to resume them, or even telling the entire computer
76 to resume. This capability goes by several names such as "Wake On
78 device is enabled for remote wakeup and it is suspended, it may resume
111 kernel will automatically resume the device (autoresume). For the
125 agent outside the USB stack: system suspend/resume (triggered by
126 userspace), manual dynamic resume (also triggered by userspace), and
248 try to resume them they disconnect themselves from the USB bus or
271 If a driver knows that its device has proper suspend/resume support,
[all …]
|
| /linux/include/linux/clk/ |
| H A D | tegra.h | 41 void (*resume)(void); member
128 if (WARN_ON(!tegra_cpu_car_ops->resume)) in tegra_cpu_clock_resume()
131 tegra_cpu_car_ops->resume(); in tegra_cpu_clock_resume()
|
| /linux/Documentation/fb/ |
| H A D | vt8623fb.rst | 25 * suspend/resume support
38 Suspend/resume works on systems that initialize video card during resume and
|
| /linux/kernel/irq/ |
| H A D | pm.c | 161 goto resume; in resume_irq()
171 resume: in resume_irq()
224 .resume = irq_pm_syscore_resume,
|
| /linux/drivers/crypto/ |
| H A D | atmel-sha.c | 147 atmel_sha_fn_t resume; member
549 atmel_sha_fn_t resume) in atmel_sha_wait_for_data_ready() argument
554 return resume(dd); in atmel_sha_wait_for_data_ready()
556 dd->resume = resume; in atmel_sha_wait_for_data_ready()
1131 dd->resume = atmel_sha_done; in atmel_sha_start()
1360 (void)dd->resume(dd); in atmel_sha_done_task()
1438 (void)atmel_sha_wait_for_data_ready(dd, dd->resume); in atmel_sha_dma_callback2()
1444 atmel_sha_fn_t resume) in atmel_sha_dma_start() argument
1454 dd->resume = resume; in atmel_sha_dma_start()
1537 dd->resume = atmel_sha_cpu_transfer; in atmel_sha_cpu_transfer()
[all …]
|