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/
45 Date: January 2012
46 Contact: Matthew Garrett <mjg@redhat.com
47 Description:
48 The BGRT is an ACPI 5.0 featur
49 to obtain a copy of the firmwa
50 some associated metadata. This
51 by boot splash applications in
52 the firmware boot splash in or
53 transitions.
54
55 image: The image bitmap. Curre
56 status: 1 if the image is vali
57 type: 0 indicates image is in
58
59 ======== =====================
60 version: The version of the BG
61 xoffset: The number of pixels
62 and the left edge of
63 yoffset: The number of pixels
64 and the top edge of t
65 ======== =====================
66
67 What: /sys/firmware/acpi/hotplug/
68 Date: February 2013
69 Contact: Rafael J. Wysocki <rafael.j.wys
70 Description:
71 There are separate hotplug pro
72 devices supported by ACPI, suc
73 processors, PCI root bridges e
74 class of devices is a collecti
75 that class of devices will be
76 code. Those profiles are repr
77 of /sys/firmware/acpi/hotplug/
78
79 The following setting is avail
80 hotplug profile:
81
82 ======== =====================
83 enabled: If set, the ACPI core
84 hotplug events associ
85 devices and will allo
86 the help of the _EJ0
87 effectively disables
88 class of devices.
89 ======== =====================
90
91 The value of the above attribu
92 or 0 (unset). Attempts to wri
93 cause -EINVAL to be returned.
94
95 What: /sys/firmware/acpi/interrupts/
96 Date: February 2008
97 Contact: Len Brown <lenb@kernel.org>
98 Description:
99 All ACPI interrupts are handle
100 the System Control Interrupt (
101 as "acpi" in /proc/interrupts.
102
103 However, one of the main funct
104 the platform understand random
105 special driver support. So wh
106 well known (fixed feature) int
107 as the power button, it can al
108 number of a "General Purpose E
109
110 A GPE vectors to a specified h
111 can do a anything the BIOS wri
112 OS context. GPE 0x12, for exa
113 to a level or edge handler cal
114 The handler may do its busines
115 Or the handler may send send a
116 to a Linux device driver regis
117 such as a battery, or a proces
118
119 To figure out where all the SC
120 /sys/firmware/acpi/interrupts
121 every possible source, and the
122 times it has triggered::
123
124 $ cd /sys/firmware/acpi/inte
125 $ grep . *
126 error: 0
127 ff_gbl_lock: 0 enabl
128 ff_pmtimer: 0 invali
129 ff_pwr_btn: 0 enabl
130 ff_rt_clk: 2 disabl
131 ff_slp_btn: 0 invali
132 gpe00: 0 invali
133 gpe01: 0 enabl
134 gpe02: 108 enabl
135 gpe03: 0 invali
136 gpe04: 0 invali
137 gpe05: 0 invali
138 gpe06: 0 enabl
139 gpe07: 0 enabl
140 gpe08: 0 invali
141 gpe09: 0 invali
142 gpe0A: 0 invali
143 gpe0B: 0 invali
144 gpe0C: 0 invali
145 gpe0D: 0 invali
146 gpe0E: 0 invali
147 gpe0F: 0 invali
148 gpe10: 0 invali
149 gpe11: 0 invali
150 gpe12: 0 invali
151 gpe13: 0 invali
152 gpe14: 0 invali
153 gpe15: 0 invali
154 gpe16: 0 invali
155 gpe17: 1084 enabl
156 gpe18: 0 enabl
157 gpe19: 0 invali
158 gpe1A: 0 invali
159 gpe1B: 0 invali
160 gpe1C: 0 invali
161 gpe1D: 0 invali
162 gpe1E: 0 invali
163 gpe1F: 0 invali
164 gpe_all: 1192
165 sci: 1194
166 sci_not: 0
167
168 =========== =================
169 sci The number of tim
170 has been called a
171
172 sci_not The number of tim
173 has been called a
174
175 gpe_all count of SCI caus
176
177 gpeXX count for individ
178
179 ff_gbl_lock Global Lock
180
181 ff_pmtimer PM Timer
182
183 ff_pwr_btn Power Button
184
185 ff_rt_clk Real Time Clock
186
187 ff_slp_btn Sleep Button
188
189 error an interrupt that
190
191 invalid it's either a GPE
192 doesn't have an e
193
194 disable the GPE/Fixed Eve
195
196 enable the GPE/Fixed Eve
197 =========== =================
198
199 Root has permission to clear a
200
201 # echo 0 > gpe11
202
203 All counters can be cleared by
204
205 # echo 0 > sci
206
207 None of these counters has an
208 of the system, they are simply
209
210 Besides this, user can also wr
211 to enable/disable/clear ACPI i
212 used to debug some ACPI interr
213
214 Note that only writing to VALI
215 i.e. user can only change the
216 Fixed Event with event handler
217
218 Let's take power button fixed
219 and other user space applicati
220 when pressing the power button
221
222 # cat ff_pwr_btn
223 0 enabled
224 # press the power button for
225 # cat ff_pwr_btn
226 3 enabled
227 # echo disable > ff_pwr_btn
228 # cat ff_pwr_btn
229 3 disabled
230 # press the power button for
231 # cat ff_pwr_btn
232 3 disabled
233 # echo enable > ff_pwr_btn
234 # cat ff_pwr_btn
235 4 enabled
236 /*
237 * this is because the statu
238 * bit is cleared, and it tr
239 * the enable bit is set aga
240 */
241 # press the power button for
242 # cat ff_pwr_btn
243 7 enabled
244 # echo disable > ff_pwr_btn
245 # press the power button for
246 # echo clear > ff_pwr_btn
247 # echo disable > ff_pwr_btn
248 # cat ff_pwr_btn
249 7 enabled
250
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.