Searched refs:noirq (Results 1 – 13 of 13) sorted by relevance
| /kernel/linux/linux-5.10/drivers/pci/pcie/ |
| 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()
374 data->noirq = true; in pcie_pme_disable_interrupt()
418 if (data->noirq) { in pcie_pme_resume()
423 data->noirq = false; in pcie_pme_resume()
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| 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.
|
| 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"
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mailbox/ |
| D | hisilicon,hi6220-mailbox.txt | 34 - hi6220,mbox-tx-noirq: Property of MCU firmware's feature, so mailbox driver
|
| D | omap-mailbox.txt | 101 - ti,mbox-send-noirq: Quirk flag to allow the client user of this sub-mailbox
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| 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,
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-power | 367 the number of times executing "noirq resume" callbacks
391 the number of times executing "noirq suspend" callbacks
|
| /kernel/linux/linux-5.10/Documentation/x86/x86_64/ |
| D | boot-options.rst | 205 acpi=noirq
|
| /kernel/linux/patches/linux-5.10/yangfan_patch/ |
| D | kernel.patch | 987 pr_err("noirq suspend of devices failed\n");
988 + log_suspend_abort_reason("noirq suspend of %s device failed",
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | am33xx-l4.dtsi | 1423 ti,mbox-send-noirq;
|
| D | am437x-l4.dtsi | 1153 ti,mbox-send-noirq;
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | kernel-parameters.txt | 3 Format: { force | on | off | strict | noirq | rsdt |
8 noirq -- do not use ACPI for IRQ routing
|