···108108 number of a "General Purpose Events" (GPE).109109110110 A GPE vectors to a specified handler in AML, which111111- can do a anything the BIOS writer wants from111111+ can do anything the BIOS writer wants from112112 OS context. GPE 0x12, for example, would vector113113 to a level or edge handler called _L12 or _E12.114114 The handler may do its business and return.115115- Or the handler may send send a Notify event115115+ Or the handler may send a Notify event116116 to a Linux device driver registered on an ACPI device,117117 such as a battery, or a processor.118118119119- To figure out where all the SCI's are coming from,119119+ To figure out where all the SCIs are coming from,120120 /sys/firmware/acpi/interrupts contains a file listing121121 every possible source, and the count of how many122122 times it has triggered::
···9292| | Low | as low, assuming active |9393+-------------+-------------+-----------------------------------------------+94949595-That said, for our above example the both GPIOs, since the bias setting9696-is explicit and _DSD is present, will be treated as active with a high9595+That said, for our above example, since the bias setting is explicit and9696+_DSD is present, both GPIOs will be treated as active with a high9797polarity and Linux will configure the pins in this state until a driver9898reprograms them differently.9999
+1-1
drivers/acpi/bus.c
···14061406 goto error1;1407140714081408 /*14091409- * Register the for all standard device notifications.14091409+ * Register for all standard device notifications.14101410 */14111411 status =14121412 acpi_install_notify_handler(ACPI_ROOT_OBJECT, ACPI_SYSTEM_NOTIFY,