Searched refs:GPE (Results 1 – 10 of 10) sorted by relevance
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):
70 number of a "General Purpose Events" (GPE).72 A GPE vectors to a specified handler in AML, which74 OS context. GPE 0x12, for example, would vector138 gpeXX - count for individual GPE source152 invalid: it's either a GPE or a Fixed Event that155 disable: the GPE/Fixed Event is valid but disabled.157 enable: the GPE/Fixed Event is valid and enabled.172 Note that only writting to VALID GPE/Fixed Event is allowed,173 i.e. user can only change the status of runtime GPE and
411 #define GPE 0x10a macro
447 #define GPE 0x10a macro
79 there are no GPE blocks defined in hardware reduced mode. This would494 Do not use GPE block devices; these are not supported in the hardware reduced495 profile used by arm64. Since there are no GPE blocks defined for use on ARM564 -- Section 9.10: GPE block devices
120 GPE(8) to be connected to the SDIO/MMC controller's SDDAT1 line.
209 be acted upon. Every GPE is associated with one or more sources of potentially210 interesting events. In particular, a GPE may be associated with a PCI device215 If a PCI device known to the system's ACPI BIOS signals wakeup, the GPE222 A GPE may be triggered when the system is sleeping (i.e. when it is in one of231 handler identifies the GPE that caused the interrupt to be generated which,363 PCI Express PME signaling and the ACPI GPE-based wakeup signaling described in
181 +-| _GPE | Scope(_GPE): the GPE namespace
2124 u8 GPE; member2184 info->irq = spmi->GPE; in try_init_spmi()
1830 u8 GPE; member