Searched refs:freeze_noirq (Results 1 – 21 of 21) sorted by relevance
| /kernel/linux/linux-5.10/drivers/base/power/ |
| D | generic_ops.c | 113 return pm && pm->freeze_noirq ? pm->freeze_noirq(dev) : 0; in pm_generic_freeze_noirq()
|
| D | main.c | 428 return ops->freeze_noirq; in pm_noirq_op()
|
| D | domain.c | 1919 genpd->domain.ops.freeze_noirq = genpd_freeze_noirq; in pm_genpd_init()
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | pm.h | 295 int (*freeze_noirq)(struct device *dev); member
332 .freeze_noirq = suspend_fn, \
|
| /kernel/linux/linux-5.10/drivers/pci/ |
| D | pci-driver.c | 1017 if (pm && pm->freeze_noirq) { in pci_pm_freeze_noirq()
1020 error = pm->freeze_noirq(dev); in pci_pm_freeze_noirq()
1021 suspend_report_result(pm->freeze_noirq, error); in pci_pm_freeze_noirq()
1346 .freeze_noirq = pci_pm_freeze_noirq,
|
| /kernel/linux/linux-5.10/drivers/thunderbolt/ |
| D | domain.c | 554 if (tb->cm_ops->freeze_noirq) in tb_domain_freeze_noirq()
555 ret = tb->cm_ops->freeze_noirq(tb); in tb_domain_freeze_noirq()
|
| D | tb.h | 378 int (*freeze_noirq)(struct tb *tb); member
|
| D | nhi.c | 1285 .freeze_noirq = nhi_freeze_noirq, /*
|
| D | tb.c | 1513 .freeze_noirq = tb_freeze_noirq,
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| 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 …]
|
| D | runtime_pm.rst | 755 - if pm_runtime_suspended(dev) returns "false", invoke the ->freeze_noirq()
789 ->resume_noirq(), ->freeze(), ->freeze_noirq(), ->thaw(), ->thaw_noirq(),
|
| /kernel/linux/linux-5.10/drivers/usb/core/ |
| D | hcd-pci.c | 618 .freeze_noirq = check_root_hub_suspended,
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| 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
|
| /kernel/linux/linux-5.10/drivers/pcmcia/ |
| D | cs.c | 876 .freeze_noirq = pcmcia_socket_dev_suspend_noirq,
|
| D | yenta_socket.c | 1347 .freeze_noirq = yenta_dev_suspend_noirq,
|
| /kernel/linux/linux-5.10/drivers/pinctrl/sirf/ |
| D | pinctrl-sirf.c | 387 .freeze_noirq = sirfsoc_pinmux_suspend_noirq,
|
| D | pinctrl-atlas7.c | 5581 .freeze_noirq = atlas7_pinmux_suspend_noirq,
6137 .freeze_noirq = atlas7_gpio_suspend_noirq,
|
| /kernel/linux/linux-5.10/drivers/hv/ |
| D | vmbus_drv.c | 1008 .freeze_noirq = vmbus_suspend,
2522 .freeze_noirq = vmbus_bus_suspend,
|
| /kernel/linux/linux-5.10/drivers/dma/ |
| D | sa11x0-dma.c | 1077 .freeze_noirq = sa11x0_dma_suspend,
|
| /kernel/linux/linux-5.10/sound/pci/hda/ |
| D | hda_intel.c | 1203 .freeze_noirq = azx_freeze_noirq,
|
| /kernel/linux/linux-5.10/drivers/tty/serial/ |
| D | imx.c | 2632 .freeze_noirq = imx_uart_suspend_noirq,
|