Home
last modified time | relevance | path

Searched refs:suspend_noirq (Results 1 – 25 of 40) sorted by relevance

12

/Linux-v5.4/drivers/thunderbolt/
Dnhi.h44 int (*suspend_noirq)(struct tb_nhi *nhi, bool wakeup); member
Dnhi_ops.c173 .suspend_noirq = icl_nhi_suspend_noirq,
Ddomain.c513 if (tb->cm_ops->suspend_noirq) in tb_domain_suspend_noirq()
514 ret = tb->cm_ops->suspend_noirq(tb); in tb_domain_suspend_noirq()
Dnhi.c874 if (nhi->ops && nhi->ops->suspend_noirq) { in __nhi_suspend_noirq()
875 ret = nhi->ops->suspend_noirq(tb->nhi, wakeup); in __nhi_suspend_noirq()
1211 .suspend_noirq = nhi_suspend_noirq,
Dtb.h272 int (*suspend_noirq)(struct tb *tb); member
Dtb.c772 .suspend_noirq = tb_suspend_noirq,
/Linux-v5.4/drivers/base/power/
Dgeneric_ops.c77 return pm && pm->suspend_noirq ? pm->suspend_noirq(dev) : 0; in pm_generic_suspend_noirq()
Dmain.c390 return ops->suspend_noirq; in pm_noirq_op()
2079 !ops->suspend_noirq && in pm_ops_is_empty()
/Linux-v5.4/arch/arm/plat-omap/
Ddebug-leds.c151 .suspend_noirq = fpga_suspend_noirq,
/Linux-v5.4/include/linux/
Dpm.h293 int (*suspend_noirq)(struct device *dev); member
330 .suspend_noirq = suspend_fn, \
/Linux-v5.4/drivers/pci/
Dpci-driver.c833 if (pm->suspend_noirq) { in pci_pm_suspend_noirq()
837 error = pm->suspend_noirq(dev); in pci_pm_suspend_noirq()
838 suspend_report_result(pm->suspend_noirq, error); in pci_pm_suspend_noirq()
846 pm->suspend_noirq); in pci_pm_suspend_noirq()
1388 .suspend_noirq = pci_pm_suspend_noirq,
/Linux-v5.4/Documentation/power/
Dpci.rst291 .suspend_noirq = pci_pm_suspend_noirq,
442 prepare, suspend, suspend_noirq.
480 returns success. Otherwise the device driver's pm->suspend_noirq() callback is
497 (pm->suspend() or pm->suspend_noirq()) saves the device's standard configuration
583 routine instead of pm->suspend_noirq(). It also doesn't attempt to prepare the
622 two phases are analogous to the suspend and suspend_noirq phases, respectively.
760 3.1.3. suspend_noirq()
763 The suspend_noirq() callback is only executed during system suspend, after
767 The difference between suspend_noirq() and suspend() is that the driver's
768 interrupt handler will not be invoked while suspend_noirq() is running. Thus
[all …]
/Linux-v5.4/Documentation/driver-api/pm/
Ddevices.rst245 and then turn its hardware as "off" as possible during suspend_noirq. The
324 the phases are: ``prepare``, ``suspend``, ``suspend_late``, ``suspend_noirq``.
350 ``suspend_noirq`` phases as well as all of the corresponding phases of
397 4. The ``suspend_noirq`` phase occurs after IRQ handlers have been disabled,
399 the callback method is running. The ``->suspend_noirq`` methods should
436 generally means undoing the actions of the ``suspend_noirq`` phase. If
467 ``suspend_noirq`` phases of system suspend and the ``resume_noirq``,
539 4. The ``freeze_noirq`` phase is analogous to the ``suspend_noirq`` phase
574 12. The ``poweroff_noirq`` phase is analogous to the ``suspend_noirq`` phase.
578 and ``->suspend_noirq`` callbacks, respectively. The only notable difference is
[all …]
/Linux-v5.4/drivers/i2c/busses/
Di2c-at91-core.c338 .suspend_noirq = at91_twi_suspend_noirq,
Di2c-lpc2k.c473 .suspend_noirq = i2c_lpc2k_suspend,
/Linux-v5.4/drivers/clocksource/
Dingenic-timer.c343 .suspend_noirq = ingenic_tcu_suspend,
/Linux-v5.4/drivers/usb/core/
Dhcd-pci.c604 .suspend_noirq = hcd_pci_suspend_noirq,
/Linux-v5.4/drivers/watchdog/
DiTCO_wdt.c620 .suspend_noirq = iTCO_wdt_suspend_noirq,
/Linux-v5.4/drivers/pcmcia/
Dcs.c877 .suspend_noirq = pcmcia_socket_dev_suspend_noirq,
/Linux-v5.4/drivers/firmware/google/
Dgsmi.c850 .suspend_noirq = gsmi_log_s0ix_suspend,
/Linux-v5.4/drivers/gpio/
Dgpio-brcmstb.c602 .suspend_noirq = brcmstb_gpio_suspend,
/Linux-v5.4/drivers/acpi/
Ddevice_pm.c1253 .suspend_noirq = acpi_subsys_suspend_noirq,
/Linux-v5.4/drivers/pinctrl/mediatek/
Dpinctrl-paris.c945 .suspend_noirq = mtk_paris_pinctrl_suspend,
Dpinctrl-mtk-common.c890 .suspend_noirq = mtk_eint_suspend,
/Linux-v5.4/drivers/pinctrl/sirf/
Dpinctrl-sirf.c385 .suspend_noirq = sirfsoc_pinmux_suspend_noirq,

12