Searched refs:GPE (Results 1 – 9 of 9) sorted by relevance
60 number of a "General Purpose Events" (GPE).62 A GPE vectors to a specified handler in AML, which64 OS context. GPE 0x12, for example, would vector128 gpeXX - count for individual GPE source142 invalid: it's either a GPE or a Fixed Event that145 disable: the GPE/Fixed Event is valid but disabled.147 enable: the GPE/Fixed Event is valid and enabled.162 Note that only writing to VALID GPE/Fixed Event is allowed,163 i.e. user can only change the status of runtime GPE and
6 General information like which GPE is assigned to the EC and whether8 Knowing the EC GPE one can watch the amount of HW events related to9 the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe):
433 #define GPE 0x10a macro
480 VXLAN_FLAG(GPE); in vxlan_flag_attr_error()
105 there are no GPE blocks defined in hardware reduced mode. This would600 Do not use GPE block devices; these are not supported in the hardware reduced601 profile used by arm64. Since there are no GPE blocks defined for use on ARM692 - Section 9.10: GPE block devices
121 GPE(8) to be connected to the SDIO/MMC controller's SDDAT1 line.
215 be acted upon. Every GPE is associated with one or more sources of potentially216 interesting events. In particular, a GPE may be associated with a PCI device221 If a PCI device known to the system's ACPI BIOS signals wakeup, the GPE228 A GPE may be triggered when the system is sleeping (i.e. when it is in one of237 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
186 +-| _GPE | Scope(_GPE): the GPE namespace
112 GPE floodings that cannot be automatically disabled by113 the GPE dispatcher.115 GPE floodings.
