Searched refs:freeze_noirq (Results 1 – 18 of 18) sorted by relevance
| /linux/drivers/base/power/ |
| A D | generic_ops.c | 113 return pm && pm->freeze_noirq ? pm->freeze_noirq(dev) : 0; in pm_generic_freeze_noirq()
|
| A D | main.c | 425 return ops->freeze_noirq; in pm_noirq_op()
|
| A D | domain.c | 1989 genpd->domain.ops.freeze_noirq = genpd_freeze_noirq; in pm_genpd_init()
|
| /linux/include/linux/ |
| A D | pm.h | 294 int (*freeze_noirq)(struct device *dev); member
331 .freeze_noirq = suspend_fn, \
|
| /linux/drivers/pci/ |
| A D | pci-driver.c | 1029 if (pm && pm->freeze_noirq) { in pci_pm_freeze_noirq()
1032 error = pm->freeze_noirq(dev); in pci_pm_freeze_noirq()
1033 suspend_report_result(pm->freeze_noirq, error); in pci_pm_freeze_noirq()
1358 .freeze_noirq = pci_pm_freeze_noirq,
|
| /linux/drivers/thunderbolt/ |
| A D | domain.c | 574 if (tb->cm_ops->freeze_noirq) in tb_domain_freeze_noirq()
575 ret = tb->cm_ops->freeze_noirq(tb); in tb_domain_freeze_noirq()
|
| A D | tb.h | 437 int (*freeze_noirq)(struct tb *tb); member
|
| A D | nhi.c | 1299 .freeze_noirq = nhi_freeze_noirq, /*
|
| A D | tb.c | 1563 .freeze_noirq = tb_freeze_noirq,
|
| /linux/Documentation/power/ |
| 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 …]
|
| A D | runtime_pm.rst | 763 - if pm_runtime_suspended(dev) returns "false", invoke the ->freeze_noirq()
797 ->resume_noirq(), ->freeze(), ->freeze_noirq(), ->thaw(), ->thaw_noirq(),
|
| /linux/drivers/usb/core/ |
| A D | hcd-pci.c | 620 .freeze_noirq = check_root_hub_suspended,
|
| /linux/Documentation/driver-api/pm/ |
| 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/ |
| A D | cs.c | 878 .freeze_noirq = pcmcia_socket_dev_suspend_noirq,
|
| A D | yenta_socket.c | 1347 .freeze_noirq = yenta_dev_suspend_noirq,
|
| /linux/drivers/hv/ |
| A D | vmbus_drv.c | 1028 .freeze_noirq = vmbus_suspend,
2605 .freeze_noirq = vmbus_bus_suspend,
|
| /linux/sound/pci/hda/ |
| A D | hda_intel.c | 1169 .freeze_noirq = azx_freeze_noirq,
|
| /linux/drivers/tty/serial/ |
| A D | imx.c | 2578 .freeze_noirq = imx_uart_suspend_noirq,
|
Completed in 53 milliseconds