Searched refs:noirq (Results 1 – 13 of 13) sorted by relevance
/openbmc/linux/drivers/pci/pcie/ |
H A D | pme.c | 45 bool noirq; /* If set, keep the PME interrupt disabled. */ member 223 if (data->noirq) in pcie_pme_work_fn() 253 if (!data->noirq) in pcie_pme_work_fn() 382 data->noirq = true; in pcie_pme_disable_interrupt() 426 if (data->noirq) { in pcie_pme_resume() 431 data->noirq = false; in pcie_pme_resume()
|
/openbmc/linux/Documentation/power/ |
H A D | suspend-and-interrupts.rst | 26 of suspend_device_irqs(), along with the "noirq" phase of device suspend and 38 suspend-resume cycle, including the "noirq" phases of suspending and resuming 101 interrupts right after the "noirq" phase of suspending devices.
|
H A D | pci.rst | 1023 reasons for doing that. Also, it causes pci_pm_suspend_late/noirq() and 1024 pci_pm_poweroff_late/noirq() to return early if the device remains in runtime 1031 "noirq" and "early" resume callbacks to be skipped if the device can be left 1035 situations. If the PM core determines that the driver's "noirq" and "early"
|
/openbmc/linux/Documentation/admin-guide/pm/ |
H A D | suspend-flows.rst | 80 *late suspend* and *noirq suspend* (see :ref:`driverapi_pm_devices` for more 88 invoked before the *noirq* suspend phase. 139 Devices are resumed in four phases called *noirq resume*, *early resume*, 146 The working-state configuration of IRQs is restored after the *noirq* resume
|
/openbmc/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | hisilicon,hi6220-mailbox.txt | 34 - hi6220,mbox-tx-noirq: Property of MCU firmware's feature, so mailbox driver
|
H A D | ti,omap-mailbox.yaml | 104 ti,mbox-send-noirq: 280 ti,mbox-send-noirq;
|
/openbmc/linux/Documentation/driver-api/pm/ |
H A D | devices.rst | 817 indicate to the PM core and middle-layer code that they allow their "noirq" and 834 has a reason to prevent the driver's "noirq" and "early" resume callbacks from 843 for the driver's "noirq" and "early" resume callbacks to be skipped. Whether or 847 If that function returns ``true``, the driver's "noirq" and "early" resume 858 ``DPM_FLAG_SMART_SUSPEND`` is set and the driver's "late" and "noirq" suspend 859 callbacks are skipped, its system-wide "noirq" and "early" resume callbacks, if 873 system-wide "noirq" and "early" resume callbacks may be skipped while its "late" 874 and "noirq" suspend callbacks may have been executed (in principle, regardless 877 callback back-to-back with its "late" and "noirq" suspend ones. [For instance,
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-power | 367 the number of times executing "noirq resume" callbacks 391 the number of times executing "noirq suspend" callbacks
|
/openbmc/linux/Documentation/arch/x86/x86_64/ |
H A D | boot-options.rst | 198 acpi=noirq
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | am33xx.dtsi | 514 ti,mbox-send-noirq;
|
/openbmc/linux/arch/arm/boot/dts/ti/omap/ |
H A D | am33xx-l4.dtsi | 1573 ti,mbox-send-noirq;
|
H A D | am437x-l4.dtsi | 1172 ti,mbox-send-noirq;
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | kernel-parameters.txt | 3 Format: { force | on | off | strict | noirq | rsdt | 8 noirq -- do not use ACPI for IRQ routing
|