Searched refs:freeze_noirq (Results 1 – 16 of 16) sorted by relevance
/linux/drivers/base/power/ |
H A D | generic_ops.c | 113 return pm && pm->freeze_noirq ? pm->freeze_noirq(dev) : 0; in pm_generic_freeze_noirq()
|
H A D | main.c | 424 return ops->freeze_noirq; in pm_noirq_op()
|
/linux/include/linux/ |
H A D | pm.h | 303 int (*freeze_noirq)(struct device *dev); member 331 .freeze_noirq = pm_sleep_ptr(suspend_fn), \
|
/linux/drivers/pci/ |
H A D | pci-driver.c | 1076 if (pm && pm->freeze_noirq) { in pci_pm_freeze_noirq() 1079 error = pm->freeze_noirq(dev); in pci_pm_freeze_noirq() 1080 suspend_report_result(dev, pm->freeze_noirq, error); in pci_pm_freeze_noirq() 1403 .freeze_noirq = pci_pm_freeze_noirq,
|
/linux/drivers/thunderbolt/ |
H A D | domain.c | 571 if (tb->cm_ops->freeze_noirq) in tb_domain_freeze_noirq() 572 ret = tb->cm_ops->freeze_noirq(tb); in tb_domain_freeze_noirq()
|
H A D | tb.h | 509 int (*freeze_noirq)(struct tb *tb); member
|
H A D | nhi.c | 1437 .freeze_noirq = nhi_freeze_noirq, /*
|
H A D | tb.c | 3131 .freeze_noirq = tb_freeze_noirq,
|
/linux/Documentation/power/ |
H A D | pci.rst | 293 .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 …]
|
H A D | runtime_pm.rst | 774 - if pm_runtime_suspended(dev) returns "false", invoke the ->freeze_noirq() 808 ->resume_noirq(), ->freeze(), ->freeze_noirq(), ->thaw(), ->thaw_noirq(),
|
/linux/Documentation/driver-api/pm/ |
H A D | devices.rst | 518 ``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/drivers/pcmcia/ |
H A D | cs.c | 877 .freeze_noirq = pcmcia_socket_dev_suspend_noirq,
|
/linux/drivers/hv/ |
H A D | vmbus_drv.c | 974 .freeze_noirq = vmbus_suspend, 2555 .freeze_noirq = vmbus_bus_suspend,
|
/linux/drivers/pmdomain/ |
H A D | core.c | 2235 genpd->domain.ops.freeze_noirq = genpd_freeze_noirq; in pm_genpd_init()
|
/linux/sound/pci/hda/ |
H A D | hda_intel.c | 1171 .freeze_noirq = pm_sleep_ptr(azx_freeze_noirq),
|
/linux/drivers/tty/serial/ |
H A D | imx.c | 2708 .freeze_noirq = imx_uart_suspend_noirq,
|