/linux-6.6.21/drivers/pinctrl/samsung/ |
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 …]
|
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-6.6.21/drivers/firmware/ |
D | qcom_scm-smc.c | 55 static void fill_wq_resume_args(struct arm_smccc_args *resume, u32 smc_call_ctx) in fill_wq_resume_args() argument 57 memset(resume->args, 0, sizeof(resume->args[0]) * ARRAY_SIZE(resume->args)); in fill_wq_resume_args() 59 resume->args[0] = ARM_SMCCC_CALL_VAL(ARM_SMCCC_STD_CALL, in fill_wq_resume_args() 63 resume->args[1] = QCOM_SCM_ARGS(1); in fill_wq_resume_args() 65 resume->args[2] = smc_call_ctx; in fill_wq_resume_args() 96 struct arm_smccc_args resume; in __scm_smc_do_quirk_handle_waitq() local 110 fill_wq_resume_args(&resume, smc_call_ctx); in __scm_smc_do_quirk_handle_waitq() 111 smc = &resume; in __scm_smc_do_quirk_handle_waitq()
|
/linux-6.6.21/drivers/base/ |
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-6.6.21/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-6.6.21/Documentation/power/ |
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.
|
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 …]
|
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 …]
|
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-6.6.21/Documentation/devicetree/bindings/arm/cpu-enable-method/ |
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-6.6.21/drivers/net/phy/ |
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,
|
D | realtek.c | 894 .resume = genphy_resume, 903 .resume = genphy_resume, 922 .resume = rtl8211b_resume, 939 .resume = genphy_resume, 949 .resume = genphy_resume, 961 .resume = rtl821x_resume, 974 .resume = rtl821x_resume, 983 .resume = rtlgen_resume, 995 .resume = rtlgen_resume, 1007 .resume = rtlgen_resume, [all …]
|
D | mxl-gpy.c | 820 .resume = genphy_resume, 838 .resume = genphy_resume, 855 .resume = genphy_resume, 873 .resume = genphy_resume, 890 .resume = genphy_resume, 908 .resume = genphy_resume, 925 .resume = genphy_resume, 943 .resume = genphy_resume, 960 .resume = genphy_resume, 977 .resume = genphy_resume, [all …]
|
/linux-6.6.21/Documentation/watchdog/ |
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-6.6.21/drivers/pnp/ |
D | driver.c | 221 if (pnp_dev->protocol->resume) { in pnp_bus_resume() 222 error = pnp_dev->protocol->resume(pnp_dev); in pnp_bus_resume() 233 if (pnp_drv->driver.pm && pnp_drv->driver.pm->resume) { in pnp_bus_resume() 234 error = pnp_drv->driver.pm->resume(dev); in pnp_bus_resume() 239 if (pnp_drv->resume) { in pnp_bus_resume() 240 error = pnp_drv->resume(pnp_dev); in pnp_bus_resume() 251 .resume = pnp_bus_resume,
|
/linux-6.6.21/arch/arm/include/asm/ |
D | outercache.h | 25 void (*resume)(void); member 102 if (outer_cache.resume) in outer_resume() 103 outer_cache.resume(); in outer_resume()
|
/linux-6.6.21/Documentation/admin-guide/pm/ |
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-6.6.21/Documentation/driver-api/pm/ |
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-6.6.21/drivers/xen/events/ |
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-6.6.21/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-6.6.21/kernel/power/ |
D | Kconfig | 51 after placing resume=/dev/swappartition on the kernel command line 64 boot, pass the 'resume=/dev/swappartition' argument to the kernel to 74 Right now you may boot without resuming and resume later but in the 96 string "Default resume partition" 100 The default resume partition is the partition that the suspend- 109 resume=/dev/<other device> 111 which will set the resume partition to the device specified. 213 bool "Test suspend/resume and wakealarm during bootup" 228 bool "Device suspend/resume watchdog" 232 locked up attempting to suspend/resume a device. [all …]
|
/linux-6.6.21/arch/arm/mach-s3c/ |
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-6.6.21/arch/x86/include/asm/ |
D | tsc.h | 56 extern void tsc_verify_tsc_adjust(bool resume); 60 static inline void tsc_verify_tsc_adjust(bool resume) { } in tsc_verify_tsc_adjust() argument
|
/linux-6.6.21/arch/mips/kernel/ |
D | r2300_switch.S | 32 LEAF(resume) 64 END(resume)
|
D | r4k_switch.S | 28 LEAF(resume) 59 END(resume)
|