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
74 sci - The number of times the ACPI SCI
75 has been called and claimed an interrupt.
77 sci_not - The number of times the ACPI SCI
78 has been called and NOT claimed an interrupt.
80 gpe_all - count of SCI caused by GPEs.
82 gpeXX - count for individual GPE source
84 ff_gbl_lock - Global Lock
88 ff_pwr_btn - Power Button
90 ff_rt_clk - Real Time Clock
92 ff_slp_btn - Sleep Button
94 error - an interrupt that can't be accounted for above.
96 invalid: it's either a GPE or a Fixed Event that
97 doesn't have an event handler.
99 disable: the GPE/Fixed Event is valid but disabled.
101 enable: the GPE/Fixed Event is valid and enabled.
103 Root has permission to clear any of these counters. Eg.
106 All counters can be cleared by clearing the total "sci":
109 None of these counters has an effect on the function
110 of the system, they are simply statistics.
112 Besides this, user can also write specific strings to these files
113 to enable/disable/clear ACPI interrupts in user space, which can be
114 used to debug some ACPI interrupt storm issues.
116 Note that only writting to VALID GPE/Fixed Event is allowed,
117 i.e. user can only change the status of runtime GPE and
118 Fixed Event with event handler installed.
120 Let's take power button fixed event for example, please kill acpid
121 and other user space applications so that the machine won't shutdown
122 when pressing the power button.
125 # press the power button for 3 times;
128 # echo disable > ff_pwr_btn
131 # press the power button for 3 times;
134 # echo enable > ff_pwr_btn
138 * this is because the status bit is set even if the enable bit is cleared,
139 * and it triggers an ACPI fixed event when the enable bit is set again
141 # press the power button for 3 times;
144 # echo disable > ff_pwr_btn
145 # press the power button for 3 times;
146 # echo clear > ff_pwr_btn /* clear the status bit */
147 # echo disable > ff_pwr_btn