forked from ~ljy/RK356X_SDK_RELEASE

blame | history | patch | commit | commitdiff
hc
2024-10-12 a5969cabbb4660eab42b6ef0412cbbd1200cf14d 
 kernel/Documentation/ABI/testing/sysfs-firmware-acpi
....@@ -12,11 +12,14 @@
1212 		image: The image bitmap. Currently a 32-bit BMP.
1313 		status: 1 if the image is valid, 0 if firmware invalidated it.
1414 		type: 0 indicates image is in BMP format.
15
+
16
+		======== ===================================================
1517 		version: The version of the BGRT. Currently 1.
1618 		xoffset: The number of pixels between the left of the screen
1719 			 and the left edge of the image.
1820 		yoffset: The number of pixels between the top of the screen
1921 			 and the top edge of the image.
22
+		======== ===================================================
2023 
2124 What:		/sys/firmware/acpi/hotplug/
2225 Date:		February 2013
....@@ -33,12 +36,14 @@
3336 		The following setting is available to user space for each
3437 		hotplug profile:
3538 
39
+		======== =======================================================
3640 		enabled: If set, the ACPI core will handle notifications of
37
-			hotplug events associated with the given class of
38
-			devices and will allow those devices to be ejected with
39
-			the help of the _EJ0 control method.  Unsetting it
40
-			effectively disables hotplug for the correspoinding
41
-			class of devices.
41
+			 hotplug events associated with the given class of
42
+			 devices and will allow those devices to be ejected with
43
+			 the help of the _EJ0 control method.  Unsetting it
44
+			 effectively disables hotplug for the correspoinding
45
+			 class of devices.
46
+		======== =======================================================
4247 
4348 		The value of the above attribute is an integer number: 1 (set)
4449 		or 0 (unset).  Attempts to write any other values to it will
....@@ -71,86 +76,90 @@
7176 		To figure out where all the SCI's are coming from,
7277 		/sys/firmware/acpi/interrupts contains a file listing
7378 		every possible source, and the count of how many
74
-		times it has triggered.
79
+		times it has triggered::
7580 
76
-		$ cd /sys/firmware/acpi/interrupts
77
-		$ grep . *
78
-		error:	     0
79
-		ff_gbl_lock:	   0   enable
80
-		ff_pmtimer:	  0  invalid
81
-		ff_pwr_btn:	  0   enable
82
-		ff_rt_clk:	 2  disable
83
-		ff_slp_btn:	  0  invalid
84
-		gpe00:	     0	invalid
85
-		gpe01:	     0	 enable
86
-		gpe02:	   108	 enable
87
-		gpe03:	     0	invalid
88
-		gpe04:	     0	invalid
89
-		gpe05:	     0	invalid
90
-		gpe06:	     0	 enable
91
-		gpe07:	     0	 enable
92
-		gpe08:	     0	invalid
93
-		gpe09:	     0	invalid
94
-		gpe0A:	     0	invalid
95
-		gpe0B:	     0	invalid
96
-		gpe0C:	     0	invalid
97
-		gpe0D:	     0	invalid
98
-		gpe0E:	     0	invalid
99
-		gpe0F:	     0	invalid
100
-		gpe10:	     0	invalid
101
-		gpe11:	     0	invalid
102
-		gpe12:	     0	invalid
103
-		gpe13:	     0	invalid
104
-		gpe14:	     0	invalid
105
-		gpe15:	     0	invalid
106
-		gpe16:	     0	invalid
107
-		gpe17:	  1084	 enable
108
-		gpe18:	     0	 enable
109
-		gpe19:	     0	invalid
110
-		gpe1A:	     0	invalid
111
-		gpe1B:	     0	invalid
112
-		gpe1C:	     0	invalid
113
-		gpe1D:	     0	invalid
114
-		gpe1E:	     0	invalid
115
-		gpe1F:	     0	invalid
116
-		gpe_all:    1192
117
-		sci:	1194
118
-		sci_not:     0	
81
+		  $ cd /sys/firmware/acpi/interrupts
82
+		  $ grep . *
83
+		  error:	     0
84
+		  ff_gbl_lock:	     0   enable
85
+		  ff_pmtimer:	     0  invalid
86
+		  ff_pwr_btn:	     0   enable
87
+		  ff_rt_clk:	     2  disable
88
+		  ff_slp_btn:	     0  invalid
89
+		  gpe00:	     0	invalid
90
+		  gpe01:	     0	 enable
91
+		  gpe02:	   108	 enable
92
+		  gpe03:	     0	invalid
93
+		  gpe04:	     0	invalid
94
+		  gpe05:	     0	invalid
95
+		  gpe06:	     0	 enable
96
+		  gpe07:	     0	 enable
97
+		  gpe08:	     0	invalid
98
+		  gpe09:	     0	invalid
99
+		  gpe0A:	     0	invalid
100
+		  gpe0B:	     0	invalid
101
+		  gpe0C:	     0	invalid
102
+		  gpe0D:	     0	invalid
103
+		  gpe0E:	     0	invalid
104
+		  gpe0F:	     0	invalid
105
+		  gpe10:	     0	invalid
106
+		  gpe11:	     0	invalid
107
+		  gpe12:	     0	invalid
108
+		  gpe13:	     0	invalid
109
+		  gpe14:	     0	invalid
110
+		  gpe15:	     0	invalid
111
+		  gpe16:	     0	invalid
112
+		  gpe17:	  1084	 enable
113
+		  gpe18:	     0	 enable
114
+		  gpe19:	     0	invalid
115
+		  gpe1A:	     0	invalid
116
+		  gpe1B:	     0	invalid
117
+		  gpe1C:	     0	invalid
118
+		  gpe1D:	     0	invalid
119
+		  gpe1E:	     0	invalid
120
+		  gpe1F:	     0	invalid
121
+		  gpe_all:	  1192
122
+		  sci:		  1194
123
+		  sci_not:	     0
119124 
120
-		sci - The number of times the ACPI SCI
121
-		has been called and claimed an interrupt.
125
+		===========  ==================================================
126
+		sci	     The number of times the ACPI SCI
127
+			     has been called and claimed an interrupt.
122128 
123
-		sci_not - The number of times the ACPI SCI
124
-		has been called and NOT claimed an interrupt.
129
+		sci_not	     The number of times the ACPI SCI
130
+			     has been called and NOT claimed an interrupt.
125131 
126
-		gpe_all - count of SCI caused by GPEs.
132
+		gpe_all	     count of SCI caused by GPEs.
127133 
128
-		gpeXX - count for individual GPE source
134
+		gpeXX	     count for individual GPE source
129135 
130
-		ff_gbl_lock - Global Lock
136
+		ff_gbl_lock  Global Lock
131137 
132
-		ff_pmtimer - PM Timer
138
+		ff_pmtimer   PM Timer
133139 
134
-		ff_pwr_btn - Power Button
140
+		ff_pwr_btn   Power Button
135141 
136
-		ff_rt_clk - Real Time Clock
142
+		ff_rt_clk    Real Time Clock
137143 
138
-		ff_slp_btn - Sleep Button
144
+		ff_slp_btn   Sleep Button
139145 
140
-		error - an interrupt that can't be accounted for above.
146
+		error	     an interrupt that can't be accounted for above.
141147 
142
-		invalid: it's either a GPE or a Fixed Event that
143
-			doesn't have an event handler.
148
+		invalid      it's either a GPE or a Fixed Event that
149
+			     doesn't have an event handler.
144150 
145
-		disable: the GPE/Fixed Event is valid but disabled.
151
+		disable	     the GPE/Fixed Event is valid but disabled.
146152 
147
-		enable: the GPE/Fixed Event is valid and enabled.
153
+		enable       the GPE/Fixed Event is valid and enabled.
154
+		===========  ==================================================
148155 
149
-		Root has permission to clear any of these counters.  Eg.
150
-		# echo 0 > gpe11
156
+		Root has permission to clear any of these counters.  Eg.::
151157 
152
-		All counters can be cleared by clearing the total "sci":
153
-		# echo 0 > sci
158
+		  # echo 0 > gpe11
159
+
160
+		All counters can be cleared by clearing the total "sci"::
161
+
162
+		  # echo 0 > sci
154163 
155164 		None of these counters has an effect on the function
156165 		of the system, they are simply statistics.
....@@ -165,32 +174,34 @@
165174 
166175 		Let's take power button fixed event for example, please kill acpid
167176 		and other user space applications so that the machine won't shutdown
168
-		when pressing the power button.
169
-		# cat ff_pwr_btn
170
-		0	enabled
171
-		# press the power button for 3 times;
172
-		# cat ff_pwr_btn
173
-		3	enabled
174
-		# echo disable > ff_pwr_btn
175
-		# cat ff_pwr_btn
176
-		3	disabled
177
-		# press the power button for 3 times;
178
-		# cat ff_pwr_btn
179
-		3	disabled
180
-		# echo enable > ff_pwr_btn
181
-		# cat ff_pwr_btn
182
-		4	enabled
183
-		/*
184
-		 * this is because the status bit is set even if the enable bit is cleared,
185
-		 * and it triggers an ACPI fixed event when the enable bit is set again
186
-		 */
187
-		# press the power button for 3 times;
188
-		# cat ff_pwr_btn
189
-		7	enabled
190
-		# echo disable > ff_pwr_btn
191
-		# press the power button for 3 times;
192
-		# echo clear > ff_pwr_btn	/* clear the status bit */
193
-		# echo disable > ff_pwr_btn
194
-		# cat ff_pwr_btn
195
-		7	enabled
177
+		when pressing the power button::
178
+
179
+		  # cat ff_pwr_btn
180
+		  0	enabled
181
+		  # press the power button for 3 times;
182
+		  # cat ff_pwr_btn
183
+		  3	enabled
184
+		  # echo disable > ff_pwr_btn
185
+		  # cat ff_pwr_btn
186
+		  3	disabled
187
+		  # press the power button for 3 times;
188
+		  # cat ff_pwr_btn
189
+		  3	disabled
190
+		  # echo enable > ff_pwr_btn
191
+		  # cat ff_pwr_btn
192
+		  4	enabled
193
+		  /*
194
+		   * this is because the status bit is set even if the enable
195
+		   * bit is cleared, and it triggers an ACPI fixed event when
196
+		   * the enable bit is set again
197
+		   */
198
+		  # press the power button for 3 times;
199
+		  # cat ff_pwr_btn
200
+		  7	enabled
201
+		  # echo disable > ff_pwr_btn
202
+		  # press the power button for 3 times;
203
+		  # echo clear > ff_pwr_btn	/* clear the status bit */
204
+		  # echo disable > ff_pwr_btn
205
+		  # cat ff_pwr_btn
206
+		  7	enabled
196207