Home
last modified time | relevance | path

Searched refs:freeze_noirq (Results 1 – 17 of 17) sorted by relevance

/linux-6.1.9/drivers/base/power/ !
Dgeneric_ops.c113 return pm && pm->freeze_noirq ? pm->freeze_noirq(dev) : 0; in pm_generic_freeze_noirq()
Dmain.c425 return ops->freeze_noirq; in pm_noirq_op()
Ddomain.c2070 genpd->domain.ops.freeze_noirq = genpd_freeze_noirq; in pm_genpd_init()
/linux-6.1.9/include/linux/ !
Dpm.h303 int (*freeze_noirq)(struct device *dev); member
331 .freeze_noirq = pm_sleep_ptr(suspend_fn), \
/linux-6.1.9/drivers/pci/ !
Dpci-driver.c1065 if (pm && pm->freeze_noirq) { in pci_pm_freeze_noirq()
1068 error = pm->freeze_noirq(dev); in pci_pm_freeze_noirq()
1069 suspend_report_result(dev, pm->freeze_noirq, error); in pci_pm_freeze_noirq()
1395 .freeze_noirq = pci_pm_freeze_noirq,
/linux-6.1.9/drivers/thunderbolt/ !
Ddomain.c566 if (tb->cm_ops->freeze_noirq) in tb_domain_freeze_noirq()
567 ret = tb->cm_ops->freeze_noirq(tb); in tb_domain_freeze_noirq()
Dtb.h470 int (*freeze_noirq)(struct tb *tb); member
Dtb.c1725 .freeze_noirq = tb_freeze_noirq,
Dnhi.c1365 .freeze_noirq = nhi_freeze_noirq, /*
/linux-6.1.9/Documentation/power/ !
Dpci.rst293 .freeze_noirq = pci_pm_freeze_noirq,
564 prepare, freeze, freeze_noirq
582 pci_pm_suspend_noirq(), but it calls the device driver's pm->freeze_noirq()
647 prepare, freeze, freeze_noirq
787 or put it into a low-power state. Still, either it or freeze_noirq() should
790 3.1.5. freeze_noirq()
793 The freeze_noirq() callback is hibernation-specific. It is executed during
802 freeze_noirq().
804 The difference between freeze_noirq() and freeze() is analogous to the
831 freeze_noirq() callbacks described above, but it does not need to save the
[all …]
Druntime_pm.rst769 - if pm_runtime_suspended(dev) returns "false", invoke the ->freeze_noirq()
803 ->resume_noirq(), ->freeze(), ->freeze_noirq(), ->thaw(), ->thaw_noirq(),
/linux-6.1.9/drivers/usb/core/ !
Dhcd-pci.c614 .freeze_noirq = check_root_hub_suspended,
/linux-6.1.9/Documentation/driver-api/pm/ !
Ddevices.rst518 ``freeze``, ``freeze_late``, ``freeze_noirq``, ``thaw_noirq``, ``thaw_early``,
535 4. The ``freeze_noirq`` phase is analogous to the ``suspend_noirq`` phase
545 the device is in the same state as at the end of the ``freeze_noirq``
577 ``freeze_noirq`` phases. Also, on many machines the firmware will power-down
610 ``prepare``, ``freeze``, and ``freeze_noirq`` phases. However, the devices
639 ``freeze_late`` and ``freeze_noirq`` phases. The device may even need to be
/linux-6.1.9/drivers/pcmcia/ !
Dcs.c876 .freeze_noirq = pcmcia_socket_dev_suspend_noirq,
/linux-6.1.9/drivers/hv/ !
Dvmbus_drv.c1024 .freeze_noirq = vmbus_suspend,
2635 .freeze_noirq = vmbus_bus_suspend,
/linux-6.1.9/sound/pci/hda/ !
Dhda_intel.c1162 .freeze_noirq = azx_freeze_noirq,
/linux-6.1.9/drivers/tty/serial/ !
Dimx.c2596 .freeze_noirq = imx_uart_suspend_noirq,