Home
last modified time | relevance | path

Searched full:pme (Results 1 – 17 of 17) sorted by relevance

/Documentation/devicetree/bindings/pci/
Dlayerscape-pcie-gen4.txt18 "pme": Asserted for pme interrupt when chip support the pme interrupt with
19 none MSI/MSI-X/INTx mode,but there is interrupt line for pme.
34 <GIC_SPI 108 IRQ_TYPE_LEVEL_HIGH>, /* PME interrupt */
36 interrupt-names = "aer", "pme", "intr";
Dfsl,layerscape-pcie-ep.yaml78 - const: pme
95 interrupts = <GIC_SPI 108 IRQ_TYPE_LEVEL_HIGH>; /* PME interrupt */
96 interrupt-names = "pme";
Dbaikal,bt1-pcie.yaml42 MSI, AER, PME, Hot-plug, Link Bandwidth Management, Link Equalization
58 - const: pme
151 "msi", "aer", "pme", "hp", "bw_mg",
Dsnps,dw-pcie.yaml180 PME message is received by the port. That means having the PME
183 const: pme
Dfsl,layerscape-pcie.yaml117 - const: pme
Dsnps,dw-pcie-common.yaml51 Complex events like VPD IO request, general AER, PME, Hot-plug, link
/Documentation/devicetree/bindings/pinctrl/
Dmarvell,orion-pinctrl.txt26 mpp2 2 gpio, pci(req3), pci-1(pme)
51 mpp2 2 gpio, pci(req3), pci-1(pme)
76 mpp2 2 gpio, pci(req3), pci(pme)
/Documentation/arch/x86/
Dearlyprintk.rst33 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
34 Status: D0 PME-Enable- DSel=0 DScale=0 PME+
/Documentation/translations/zh_CN/PCI/
Dpciebus-howto.rst41 其端口类型。PCI Express端口的服务包括本地热拔插支持(HP)、电源管理事件支持(PME)、
183 PCI Express电源管理(PME)、高级错误报告(AER)、热插拔(HP)和虚拟通道(VC)的服务
/Documentation/devicetree/bindings/net/dsa/
Dmicrochip,ksz.yaml56 microchip,pme-active-high:
59 Indicates if the PME pin polarity is active-high.
/Documentation/devicetree/bindings/net/
Dsmsc,lan9115.yaml43 Optional PME (power management event) interrupt that is able to wake
/Documentation/devicetree/bindings/soc/fsl/
Dfsl,qman-portal.yaml68 '^(fman0|fman1|pme|crypto)+$':
/Documentation/PCI/
Dpciebus-howto.rst35 power management event support (PME), advanced error reporting
205 Service drivers for PCI Express Power Management (PME), Advanced
/Documentation/power/
Dpci.rst52 requiring the device to be active. After receiving a PME the kernel is supposed
55 delivering the PME from the device to the CPU and the operating system kernel.
253 interrupt whenever it receives a PME message from one of the devices below it.
254 The PCI Express Requester ID of the device that sent the PME message is then
256 read by the interrupt handler allowing the device to be identified. [PME
261 In principle the native PCI Express PME signaling may also be used on ACPI-based
266 the native PCI Express PME signaling cannot be used by the kernel in that case.
316 unsigned int pme_support:5; /* Bitmask of states from which PME#
318 unsigned int pme_poll:1; /* Poll device's PME status bit */
372 PCI Express PME signaling and the ACPI GPE-based wakeup signaling described in
Druntime_pm.rst114 PCI PME) for proper functioning and device_can_wakeup() returns 'false' for the
/Documentation/driver-api/pm/
Ddevices.rst417 and :c:func:`pci_enable_wake()` does something similar for the PCI PME signal.
672 issues would be issued through the PME# bus signal. Plus, there are
/Documentation/admin-guide/
Dkernel-parameters.txt4744 native Use native PCIe services (PME, AER, DPC, PCIe hotplug)
4750 compat Disable native PCIe services (PME, AER, DPC, PCIe
4757 pcie_pme= [PCIE,PM] Native PCIe PME signaling options:
4758 nomsi Do not use MSI for native PCIe PME signaling (this makes