Searched full:gpe (Results 1 – 16 of 16) sorted by relevance
| /Documentation/ABI/testing/ |
| D | debugfs-ec | 1 What: /sys/kernel/debug/ec/*/{gpe,use_global_lock,io}
6 General information like which GPE is assigned to the EC and whether
8 Knowing the EC GPE one can watch the amount of HW events related to
9 the EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`):
|
| D | sysfs-firmware-acpi | 108 number of a "General Purpose Events" (GPE).
110 A GPE vectors to a specified handler in AML, which
112 OS context. GPE 0x12, for example, would vector
177 gpeXX count for individual GPE source
191 invalid it's either a GPE or a Fixed Event that
194 disable the GPE/Fixed Event is valid but disabled.
196 enable the GPE/Fixed Event is valid and enabled.
214 Note that only writing to VALID GPE/Fixed Event is allowed,
215 i.e. user can only change the status of runtime GPE and
|
| /Documentation/networking/ |
| D | vxlan.rst | 86 Types: geneve, vxlan-gpe
88 port 1230, vxlan-gpe
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | focaltech,gpt3.yaml | 45 reset-gpios = <&gpe 2 GPIO_ACTIVE_LOW>;
|
| D | leadtek,ltk035c5444t.yaml | 49 reset-gpios = <&gpe 2 GPIO_ACTIVE_LOW>;
|
| D | abt,y030xx067a.yaml | 50 reset-gpios = <&gpe 2 GPIO_ACTIVE_LOW>;
|
| D | innolux,ej030na.yaml | 50 reset-gpios = <&gpe 4 GPIO_ACTIVE_LOW>;
|
| D | kingdisplay,kd035g6-54nt.yaml | 52 reset-gpios = <&gpe 2 GPIO_ACTIVE_LOW>;
|
| D | auo,a030jtn01.yaml | 49 reset-gpios = <&gpe 4 GPIO_ACTIVE_LOW>;
|
| D | fascontek,fs035vg158.yaml | 48 reset-gpios = <&gpe 2 GPIO_ACTIVE_LOW>;
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ingenic,nemc.yaml | 92 interrupt-parent = <&gpe>;
|
| /Documentation/arch/arm64/ |
| D | acpi_object_usage.rst | 133 there are no GPE blocks defined in hardware reduced mode. This would
671 Do not use GPE block devices; these are not supported in the hardware reduced
672 profile used by arm64. Since there are no GPE blocks defined for use on ARM
763 - Section 9.10: GPE block devices
|
| /Documentation/power/ |
| D | pci.rst | 215 be acted upon. Every GPE is associated with one or more sources of potentially
216 interesting events. In particular, a GPE may be associated with a PCI device
221 If a PCI device known to the system's ACPI BIOS signals wakeup, the GPE
228 A GPE may be triggered when the system is sleeping (i.e. when it is in one of
237 handler identifies the GPE that caused the interrupt to be generated which,
372 PCI Express PME signaling and the ACPI GPE-based wakeup signaling described in
|
| /Documentation/firmware-guide/acpi/ |
| D | namespace.rst | 186 +-| _GPE | Scope(_GPE): the GPE namespace
|
| /Documentation/netlink/specs/ |
| D | ethtool.yaml | 14 entries: [ vxlan, geneve, vxlan-gpe ]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 127 GPE floodings that cannot be automatically disabled by
128 the GPE dispatcher.
130 GPE floodings.
|