1 What: /sys/firmware/acpi/interrupts/
3 Contact: Len Brown <lenb@kernel.org>
5 All ACPI interrupts are handled via a single IRQ,
6 the System Control Interrupt (SCI), which appears
7 as "acpi" in /proc/interrupts.
9 However, one of the main functions of ACPI is to make
10 the platform understand random hardware without
11 special driver support. So while the SCI handles a few
12 well known (fixed feature) interrupts sources, such
13 as the power button, it can also handle a variable
14 number of a "General Purpose Events" (GPE).
16 A GPE vectors to a specified handler in AML, which
17 can do a anything the BIOS writer wants from
18 OS context. GPE 0x12, for example, would vector
19 to a level or edge handler called _L12 or _E12.
20 The handler may do its business and return.
21 Or the handler may send send a Notify event
22 to a Linux device driver registered on an ACPI device,
23 such as a battery, or a processor.
25 To figure out where all the SCI's are coming from,
26 /sys/firmware/acpi/interrupts contains a file listing
27 every possible source, and the count of how many
28 times it has triggered.
30 $ cd /sys/firmware/acpi/interrupts
73 sci - The total number of times the ACPI SCI
74 has claimed an interrupt.
76 gpe_all - count of SCI caused by GPEs.
78 gpeXX - count for individual GPE source
80 ff_gbl_lock - Global Lock
84 ff_pwr_btn - Power Button
86 ff_rt_clk - Real Time Clock
88 ff_slp_btn - Sleep Button
90 error - an interrupt that can't be accounted for above.
92 Root has permission to clear any of these counters. Eg.
95 All counters can be cleared by clearing the total "sci":
98 None of these counters has an effect on the function
99 of the system, they are simply statistics.