1 What: /sys/firmware/acpi/fpdt/ <<
2 Date: Jan 2021 <<
3 Contact: Zhang Rui <rui.zhang@intel.com> <<
4 Description: <<
5 ACPI Firmware Performance Data <<
6 information for firmware perfo <<
7 S3 suspend and S3 resume. This <<
8 performance data retrieved fro <<
9 <<
10 boot: <<
11 firmware_start_ns: Tim <<
12 of firmware im <<
13 bootloader_load_ns: Ti <<
14 loading the OS <<
15 In nanoseconds <<
16 bootloader_launch_ns: <<
17 launching the <<
18 image. In nano <<
19 exitbootservice_start_ <<
20 point when the <<
21 ExitBootServic <<
22 firmware. In n <<
23 exitbootservice_end_ns <<
24 just prior to <<
25 back from the <<
26 UEFI compatibl <<
27 suspend: <<
28 suspend_start_ns: Time <<
29 OS write to SL <<
30 nanoseconds. <<
31 suspend_end_ns: Timer <<
32 firmware write <<
33 hardware entry <<
34 resume: <<
35 resume_count: A count <<
36 since the last <<
37 resume_avg_ns: Average <<
38 logged since t <<
39 including the <<
40 resume_prev_ns: Timer <<
41 platform runti <<
42 handoff to the <<
43 <<
44 What: /sys/firmware/acpi/bgrt/ 1 What: /sys/firmware/acpi/bgrt/
45 Date: January 2012 2 Date: January 2012
46 Contact: Matthew Garrett <mjg@redhat.com 3 Contact: Matthew Garrett <mjg@redhat.com>
47 Description: 4 Description:
48 The BGRT is an ACPI 5.0 featur 5 The BGRT is an ACPI 5.0 feature that allows the OS
49 to obtain a copy of the firmwa 6 to obtain a copy of the firmware boot splash and
50 some associated metadata. This 7 some associated metadata. This is intended to be used
51 by boot splash applications in 8 by boot splash applications in order to interact with
52 the firmware boot splash in or 9 the firmware boot splash in order to avoid jarring
53 transitions. 10 transitions.
54 11
55 image: The image bitmap. Curre 12 image: The image bitmap. Currently a 32-bit BMP.
56 status: 1 if the image is vali 13 status: 1 if the image is valid, 0 if firmware invalidated it.
57 type: 0 indicates image is in 14 type: 0 indicates image is in BMP format.
58 <<
59 ======== ===================== <<
60 version: The version of the BG 15 version: The version of the BGRT. Currently 1.
61 xoffset: The number of pixels 16 xoffset: The number of pixels between the left of the screen
62 and the left edge of 17 and the left edge of the image.
63 yoffset: The number of pixels 18 yoffset: The number of pixels between the top of the screen
64 and the top edge of t 19 and the top edge of the image.
65 ======== ===================== <<
66 20
67 What: /sys/firmware/acpi/hotplug/ 21 What: /sys/firmware/acpi/hotplug/
68 Date: February 2013 22 Date: February 2013
69 Contact: Rafael J. Wysocki <rafael.j.wys 23 Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
70 Description: 24 Description:
71 There are separate hotplug pro 25 There are separate hotplug profiles for different classes of
72 devices supported by ACPI, suc 26 devices supported by ACPI, such as containers, memory modules,
73 processors, PCI root bridges e 27 processors, PCI root bridges etc. A hotplug profile for a given
74 class of devices is a collecti 28 class of devices is a collection of settings defining the way
75 that class of devices will be 29 that class of devices will be handled by the ACPI core hotplug
76 code. Those profiles are repr 30 code. Those profiles are represented in sysfs as subdirectories
77 of /sys/firmware/acpi/hotplug/ 31 of /sys/firmware/acpi/hotplug/.
78 32
79 The following setting is avail 33 The following setting is available to user space for each
80 hotplug profile: 34 hotplug profile:
81 35
82 ======== ===================== <<
83 enabled: If set, the ACPI core 36 enabled: If set, the ACPI core will handle notifications of
84 hotplug events associ !! 37 hotplug events associated with the given class of
85 devices and will allo !! 38 devices and will allow those devices to be ejected with
86 the help of the _EJ0 !! 39 the help of the _EJ0 control method. Unsetting it
87 effectively disables !! 40 effectively disables hotplug for the correspoinding
88 class of devices. !! 41 class of devices.
89 ======== ===================== <<
90 42
91 The value of the above attribu 43 The value of the above attribute is an integer number: 1 (set)
92 or 0 (unset). Attempts to wri 44 or 0 (unset). Attempts to write any other values to it will
93 cause -EINVAL to be returned. 45 cause -EINVAL to be returned.
94 46
>> 47 What: /sys/firmware/acpi/hotplug/force_remove
>> 48 Date: May 2013
>> 49 Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> 50 Description:
>> 51 The number in this file (0 or 1) determines whether (1) or not
>> 52 (0) the ACPI subsystem will allow devices to be hot-removed even
>> 53 if they cannot be put offline gracefully (from the kernel's
>> 54 viewpoint). That number can be changed by writing a boolean
>> 55 value to this file.
>> 56
95 What: /sys/firmware/acpi/interrupts/ 57 What: /sys/firmware/acpi/interrupts/
96 Date: February 2008 58 Date: February 2008
97 Contact: Len Brown <lenb@kernel.org> 59 Contact: Len Brown <lenb@kernel.org>
98 Description: 60 Description:
99 All ACPI interrupts are handle 61 All ACPI interrupts are handled via a single IRQ,
100 the System Control Interrupt ( 62 the System Control Interrupt (SCI), which appears
101 as "acpi" in /proc/interrupts. 63 as "acpi" in /proc/interrupts.
102 64
103 However, one of the main funct 65 However, one of the main functions of ACPI is to make
104 the platform understand random 66 the platform understand random hardware without
105 special driver support. So wh 67 special driver support. So while the SCI handles a few
106 well known (fixed feature) int 68 well known (fixed feature) interrupts sources, such
107 as the power button, it can al 69 as the power button, it can also handle a variable
108 number of a "General Purpose E 70 number of a "General Purpose Events" (GPE).
109 71
110 A GPE vectors to a specified h 72 A GPE vectors to a specified handler in AML, which
111 can do a anything the BIOS wri 73 can do a anything the BIOS writer wants from
112 OS context. GPE 0x12, for exa 74 OS context. GPE 0x12, for example, would vector
113 to a level or edge handler cal 75 to a level or edge handler called _L12 or _E12.
114 The handler may do its busines 76 The handler may do its business and return.
115 Or the handler may send send a 77 Or the handler may send send a Notify event
116 to a Linux device driver regis 78 to a Linux device driver registered on an ACPI device,
117 such as a battery, or a proces 79 such as a battery, or a processor.
118 80
119 To figure out where all the SC 81 To figure out where all the SCI's are coming from,
120 /sys/firmware/acpi/interrupts 82 /sys/firmware/acpi/interrupts contains a file listing
121 every possible source, and the 83 every possible source, and the count of how many
122 times it has triggered:: !! 84 times it has triggered.
123 85
124 $ cd /sys/firmware/acpi/inte !! 86 $ cd /sys/firmware/acpi/interrupts
125 $ grep . * !! 87 $ grep . *
126 error: 0 !! 88 error: 0
127 ff_gbl_lock: 0 enabl !! 89 ff_gbl_lock: 0 enable
128 ff_pmtimer: 0 invali !! 90 ff_pmtimer: 0 invalid
129 ff_pwr_btn: 0 enabl !! 91 ff_pwr_btn: 0 enable
130 ff_rt_clk: 2 disabl !! 92 ff_rt_clk: 2 disable
131 ff_slp_btn: 0 invali !! 93 ff_slp_btn: 0 invalid
132 gpe00: 0 invali !! 94 gpe00: 0 invalid
133 gpe01: 0 enabl !! 95 gpe01: 0 enable
134 gpe02: 108 enabl !! 96 gpe02: 108 enable
135 gpe03: 0 invali !! 97 gpe03: 0 invalid
136 gpe04: 0 invali !! 98 gpe04: 0 invalid
137 gpe05: 0 invali !! 99 gpe05: 0 invalid
138 gpe06: 0 enabl !! 100 gpe06: 0 enable
139 gpe07: 0 enabl !! 101 gpe07: 0 enable
140 gpe08: 0 invali !! 102 gpe08: 0 invalid
141 gpe09: 0 invali !! 103 gpe09: 0 invalid
142 gpe0A: 0 invali !! 104 gpe0A: 0 invalid
143 gpe0B: 0 invali !! 105 gpe0B: 0 invalid
144 gpe0C: 0 invali !! 106 gpe0C: 0 invalid
145 gpe0D: 0 invali !! 107 gpe0D: 0 invalid
146 gpe0E: 0 invali !! 108 gpe0E: 0 invalid
147 gpe0F: 0 invali !! 109 gpe0F: 0 invalid
148 gpe10: 0 invali !! 110 gpe10: 0 invalid
149 gpe11: 0 invali !! 111 gpe11: 0 invalid
150 gpe12: 0 invali !! 112 gpe12: 0 invalid
151 gpe13: 0 invali !! 113 gpe13: 0 invalid
152 gpe14: 0 invali !! 114 gpe14: 0 invalid
153 gpe15: 0 invali !! 115 gpe15: 0 invalid
154 gpe16: 0 invali !! 116 gpe16: 0 invalid
155 gpe17: 1084 enabl !! 117 gpe17: 1084 enable
156 gpe18: 0 enabl !! 118 gpe18: 0 enable
157 gpe19: 0 invali !! 119 gpe19: 0 invalid
158 gpe1A: 0 invali !! 120 gpe1A: 0 invalid
159 gpe1B: 0 invali !! 121 gpe1B: 0 invalid
160 gpe1C: 0 invali !! 122 gpe1C: 0 invalid
161 gpe1D: 0 invali !! 123 gpe1D: 0 invalid
162 gpe1E: 0 invali !! 124 gpe1E: 0 invalid
163 gpe1F: 0 invali !! 125 gpe1F: 0 invalid
164 gpe_all: 1192 !! 126 gpe_all: 1192
165 sci: 1194 !! 127 sci: 1194
166 sci_not: 0 !! 128 sci_not: 0
167 !! 129
168 =========== ================= !! 130 sci - The number of times the ACPI SCI
169 sci The number of tim !! 131 has been called and claimed an interrupt.
170 has been called a !! 132
171 !! 133 sci_not - The number of times the ACPI SCI
172 sci_not The number of tim !! 134 has been called and NOT claimed an interrupt.
173 has been called a !! 135
174 !! 136 gpe_all - count of SCI caused by GPEs.
175 gpe_all count of SCI caus !! 137
176 !! 138 gpeXX - count for individual GPE source
177 gpeXX count for individ !! 139
178 !! 140 ff_gbl_lock - Global Lock
179 ff_gbl_lock Global Lock !! 141
180 !! 142 ff_pmtimer - PM Timer
181 ff_pmtimer PM Timer !! 143
182 !! 144 ff_pwr_btn - Power Button
183 ff_pwr_btn Power Button !! 145
184 !! 146 ff_rt_clk - Real Time Clock
185 ff_rt_clk Real Time Clock !! 147
186 !! 148 ff_slp_btn - Sleep Button
187 ff_slp_btn Sleep Button !! 149
188 !! 150 error - an interrupt that can't be accounted for above.
189 error an interrupt that !! 151
190 !! 152 invalid: it's either a GPE or a Fixed Event that
191 invalid it's either a GPE !! 153 doesn't have an event handler.
192 doesn't have an e !! 154
193 !! 155 disable: the GPE/Fixed Event is valid but disabled.
194 disable the GPE/Fixed Eve <<
195 <<
196 enable the GPE/Fixed Eve <<
197 =========== ================= <<
198 156
199 Root has permission to clear a !! 157 enable: the GPE/Fixed Event is valid and enabled.
200 158
201 # echo 0 > gpe11 !! 159 Root has permission to clear any of these counters. Eg.
>> 160 # echo 0 > gpe11
202 161
203 All counters can be cleared by !! 162 All counters can be cleared by clearing the total "sci":
204 !! 163 # echo 0 > sci
205 # echo 0 > sci <<
206 164
207 None of these counters has an 165 None of these counters has an effect on the function
208 of the system, they are simply 166 of the system, they are simply statistics.
209 167
210 Besides this, user can also wr 168 Besides this, user can also write specific strings to these files
211 to enable/disable/clear ACPI i 169 to enable/disable/clear ACPI interrupts in user space, which can be
212 used to debug some ACPI interr 170 used to debug some ACPI interrupt storm issues.
213 171
214 Note that only writing to VALI 172 Note that only writing to VALID GPE/Fixed Event is allowed,
215 i.e. user can only change the 173 i.e. user can only change the status of runtime GPE and
216 Fixed Event with event handler 174 Fixed Event with event handler installed.
217 175
218 Let's take power button fixed 176 Let's take power button fixed event for example, please kill acpid
219 and other user space applicati 177 and other user space applications so that the machine won't shutdown
220 when pressing the power button !! 178 when pressing the power button.
221 !! 179 # cat ff_pwr_btn
222 # cat ff_pwr_btn !! 180 0 enabled
223 0 enabled !! 181 # press the power button for 3 times;
224 # press the power button for !! 182 # cat ff_pwr_btn
225 # cat ff_pwr_btn !! 183 3 enabled
226 3 enabled !! 184 # echo disable > ff_pwr_btn
227 # echo disable > ff_pwr_btn !! 185 # cat ff_pwr_btn
228 # cat ff_pwr_btn !! 186 3 disabled
229 3 disabled !! 187 # press the power button for 3 times;
230 # press the power button for !! 188 # cat ff_pwr_btn
231 # cat ff_pwr_btn !! 189 3 disabled
232 3 disabled !! 190 # echo enable > ff_pwr_btn
233 # echo enable > ff_pwr_btn !! 191 # cat ff_pwr_btn
234 # cat ff_pwr_btn !! 192 4 enabled
235 4 enabled !! 193 /*
236 /* !! 194 * this is because the status bit is set even if the enable bit is cleared,
237 * this is because the statu !! 195 * and it triggers an ACPI fixed event when the enable bit is set again
238 * bit is cleared, and it tr !! 196 */
239 * the enable bit is set aga !! 197 # press the power button for 3 times;
240 */ !! 198 # cat ff_pwr_btn
241 # press the power button for !! 199 7 enabled
242 # cat ff_pwr_btn !! 200 # echo disable > ff_pwr_btn
243 7 enabled !! 201 # press the power button for 3 times;
244 # echo disable > ff_pwr_btn !! 202 # echo clear > ff_pwr_btn /* clear the status bit */
245 # press the power button for !! 203 # echo disable > ff_pwr_btn
246 # echo clear > ff_pwr_btn !! 204 # cat ff_pwr_btn
247 # echo disable > ff_pwr_btn !! 205 7 enabled
248 # cat ff_pwr_btn <<
249 7 enabled <<
250 206
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.