1 **General Properties** !! 1 ===== General Properties =====
2 2
3 What: /sys/class/power_supply/<suppl 3 What: /sys/class/power_supply/<supply_name>/manufacturer
4 Date: May 2007 4 Date: May 2007
5 Contact: linux-pm@vger.kernel.org 5 Contact: linux-pm@vger.kernel.org
6 Description: 6 Description:
7 Reports the name of the device 7 Reports the name of the device manufacturer.
8 8
9 Access: Read 9 Access: Read
10 Valid values: Represented as s 10 Valid values: Represented as string
11 11
12 What: /sys/class/power_supply/<suppl 12 What: /sys/class/power_supply/<supply_name>/model_name
13 Date: May 2007 13 Date: May 2007
14 Contact: linux-pm@vger.kernel.org 14 Contact: linux-pm@vger.kernel.org
15 Description: 15 Description:
16 Reports the name of the device 16 Reports the name of the device model.
17 17
18 Access: Read 18 Access: Read
19 Valid values: Represented as s 19 Valid values: Represented as string
20 20
21 What: /sys/class/power_supply/<suppl 21 What: /sys/class/power_supply/<supply_name>/serial_number
22 Date: January 2008 22 Date: January 2008
23 Contact: linux-pm@vger.kernel.org 23 Contact: linux-pm@vger.kernel.org
24 Description: 24 Description:
25 Reports the serial number of t 25 Reports the serial number of the device.
26 26
27 Access: Read 27 Access: Read
28 Valid values: Represented as s 28 Valid values: Represented as string
29 29
30 What: /sys/class/power_supply/<suppl 30 What: /sys/class/power_supply/<supply_name>/type
31 Date: May 2010 31 Date: May 2010
32 Contact: linux-pm@vger.kernel.org 32 Contact: linux-pm@vger.kernel.org
33 Description: 33 Description:
34 Describes the main type of the 34 Describes the main type of the supply.
35 35
36 Access: Read 36 Access: Read
37 Valid values: "Battery", "UPS" !! 37 Valid values: "Battery", "UPS", "Mains", "USB"
38 38
39 **Battery and USB properties** !! 39 ===== Battery Properties =====
40 <<
41 What: /sys/class/power_supply/<suppl <<
42 Date: May 2007 <<
43 Contact: linux-pm@vger.kernel.org <<
44 Description: <<
45 Battery: <<
46 <<
47 Reports an average IBAT curr <<
48 a fixed period. Normally dev <<
49 in which they average readin <<
50 value. <<
51 <<
52 USB: <<
53 <<
54 Reports an average IBUS curr <<
55 Normally devices will provid <<
56 average readings to smooth o <<
57 <<
58 Access: Read <<
59 <<
60 Valid values: Represented in m <<
61 used for discharging batteries <<
62 batteries and for USB IBUS cur <<
63 <<
64 What: /sys/class/power_supply/<suppl <<
65 Date: October 2010 <<
66 Contact: linux-pm@vger.kernel.org <<
67 Description: <<
68 Battery: <<
69 <<
70 Reports the maximum IBAT cur <<
71 <<
72 USB: <<
73 <<
74 Reports the maximum IBUS cur <<
75 <<
76 Access: Read <<
77 Valid values: Represented in m <<
78 <<
79 What: /sys/class/power_supply/<suppl <<
80 Date: May 2007 <<
81 Contact: linux-pm@vger.kernel.org <<
82 Description: <<
83 <<
84 Battery: <<
85 <<
86 Reports an instant, single I <<
87 battery. This value is not a <<
88 <<
89 Access: Read <<
90 <<
91 USB: <<
92 <<
93 Reports the IBUS current sup <<
94 read-only reporting, unless <<
95 is set to be programmable, i <<
96 within the reported min/max <<
97 <<
98 Access: Read, Write <<
99 <<
100 Valid values: Represented in m <<
101 used for discharging batteries <<
102 batteries and for USB IBUS cur <<
103 <<
104 What: /sys/class/power_supply/<suppl <<
105 Date: May 2007 <<
106 Contact: linux-pm@vger.kernel.org <<
107 Description: <<
108 Battery: <<
109 <<
110 Reports the current TBAT bat <<
111 <<
112 USB: <<
113 <<
114 Reports the current supply t <<
115 normally be the internal tem <<
116 (e.g TJUNC temperature of an <<
117 <<
118 Access: Read <<
119 <<
120 Valid values: Represented in 1 <<
121 <<
122 What: /sys/class/power_supply/<suppl <<
123 Date: July 2012 <<
124 Contact: linux-pm@vger.kernel.org <<
125 Description: <<
126 Battery: <<
127 <<
128 Maximum TBAT temperature tri <<
129 notify user-space of the eve <<
130 <<
131 USB: <<
132 <<
133 Maximum supply temperature t <<
134 will notify user-space of th <<
135 <<
136 This is normally used for the <<
137 user-space needs to know if th <<
138 upper threshold so it can take <<
139 user that the temperature is c <<
140 stopped). <<
141 <<
142 Access: Read <<
143 <<
144 Valid values: Represented in 1 <<
145 <<
146 What: /sys/class/power_supply/<suppl <<
147 Date: July 2012 <<
148 Contact: linux-pm@vger.kernel.org <<
149 Description: <<
150 <<
151 Battery: <<
152 <<
153 Minimum TBAT temperature tri <<
154 notify user-space of the eve <<
155 <<
156 USB: <<
157 <<
158 Minimum supply temperature t <<
159 will notify user-space of th <<
160 <<
161 This is normally used for the <<
162 needs to know if the temperatu <<
163 so it can take appropriate act <<
164 temperature level is high, and <<
165 reduced accordingly to remedy <<
166 <<
167 Access: Read <<
168 <<
169 Valid values: Represented in 1 <<
170 <<
171 What: /sys/class/power_supply/<suppl <<
172 Date: July 2014 <<
173 Contact: linux-pm@vger.kernel.org <<
174 Description: <<
175 Battery: <<
176 <<
177 Reports the maximum allowed <<
178 charging. <<
179 <<
180 USB: <<
181 <<
182 Reports the maximum allowed <<
183 <<
184 Access: Read <<
185 <<
186 Valid values: Represented in 1 <<
187 <<
188 What: /sys/class/power_supply/<suppl <<
189 Date: July 2014 <<
190 Contact: linux-pm@vger.kernel.org <<
191 Description: <<
192 Battery: <<
193 <<
194 Reports the minimum allowed <<
195 charging. <<
196 <<
197 USB: <<
198 <<
199 Reports the minimum allowed <<
200 <<
201 Access: Read <<
202 <<
203 Valid values: Represented in 1 <<
204 <<
205 What: /sys/class/power_supply/<suppl <<
206 Date: January 2008 <<
207 Contact: linux-pm@vger.kernel.org <<
208 Description: <<
209 Battery: <<
210 <<
211 Reports the maximum safe VBA <<
212 battery, during charging. <<
213 <<
214 USB: <<
215 <<
216 Reports the maximum VBUS vol <<
217 <<
218 Access: Read <<
219 <<
220 Valid values: Represented in m <<
221 <<
222 What: /sys/class/power_supply/<suppl <<
223 Date: January 2008 <<
224 Contact: linux-pm@vger.kernel.org <<
225 Description: <<
226 Battery: <<
227 <<
228 Reports the minimum safe VBA <<
229 battery, during discharging. <<
230 <<
231 USB: <<
232 <<
233 Reports the minimum VBUS vol <<
234 <<
235 Access: Read <<
236 <<
237 Valid values: Represented in m <<
238 <<
239 What: /sys/class/power_supply/<suppl <<
240 Date: May 2007 <<
241 Contact: linux-pm@vger.kernel.org <<
242 Description: <<
243 Battery: <<
244 <<
245 Reports an instant, single V <<
246 battery. This value is not a <<
247 <<
248 Access: Read <<
249 <<
250 USB: <<
251 <<
252 Reports the VBUS voltage sup <<
253 read-only reporting, unless <<
254 is set to be programmable, i <<
255 within the reported min/max <<
256 <<
257 Access: Read, Write <<
258 <<
259 Valid values: Represented in m <<
260 <<
261 **Battery Properties** <<
262 40
263 What: /sys/class/power_supply/<suppl 41 What: /sys/class/power_supply/<supply_name>/capacity
264 Date: May 2007 42 Date: May 2007
265 Contact: linux-pm@vger.kernel.org 43 Contact: linux-pm@vger.kernel.org
266 Description: 44 Description:
267 Fine grain representation of b 45 Fine grain representation of battery capacity.
268 <<
269 Access: Read 46 Access: Read
270 <<
271 Valid values: 0 - 100 (percent 47 Valid values: 0 - 100 (percent)
272 48
273 What: /sys/class/power_supply/<suppl 49 What: /sys/class/power_supply/<supply_name>/capacity_alert_max
274 Date: July 2012 50 Date: July 2012
275 Contact: linux-pm@vger.kernel.org 51 Contact: linux-pm@vger.kernel.org
276 Description: 52 Description:
277 Maximum battery capacity trip- 53 Maximum battery capacity trip-wire value where the supply will
278 notify user-space of the event 54 notify user-space of the event. This is normally used for the
279 battery discharging scenario w 55 battery discharging scenario where user-space needs to know the
280 battery has dropped to an uppe 56 battery has dropped to an upper level so it can take
281 appropriate action (e.g. warni 57 appropriate action (e.g. warning user that battery level is
282 low). 58 low).
283 59
284 Access: Read, Write 60 Access: Read, Write
285 <<
286 Valid values: 0 - 100 (percent 61 Valid values: 0 - 100 (percent)
287 62
288 What: /sys/class/power_supply/<suppl 63 What: /sys/class/power_supply/<supply_name>/capacity_alert_min
289 Date: July 2012 64 Date: July 2012
290 Contact: linux-pm@vger.kernel.org 65 Contact: linux-pm@vger.kernel.org
291 Description: 66 Description:
292 Minimum battery capacity trip- 67 Minimum battery capacity trip-wire value where the supply will
293 notify user-space of the event 68 notify user-space of the event. This is normally used for the
294 battery discharging scenario w 69 battery discharging scenario where user-space needs to know the
295 battery has dropped to a lower 70 battery has dropped to a lower level so it can take
296 appropriate action (e.g. warni 71 appropriate action (e.g. warning user that battery level is
297 critically low). 72 critically low).
298 73
299 Access: Read, Write 74 Access: Read, Write
300 <<
301 Valid values: 0 - 100 (percent 75 Valid values: 0 - 100 (percent)
302 76
303 What: /sys/class/power_supply/<suppl !! 77 What: /sys/class/power_supply/<supply_name>/capacity_level
304 Date: April 2019 !! 78 Date: June 2009
305 Contact: linux-pm@vger.kernel.org 79 Contact: linux-pm@vger.kernel.org
306 Description: 80 Description:
307 Battery capacity measurement b !! 81 Coarse representation of battery capacity.
308 recalibration. This values pro <<
309 margin expected to exist by th <<
310 Values close to 0% will be ret <<
311 has happened. Over time the er <<
312 100% means, that the capacity <<
313 completely useless. <<
314 82
315 Access: Read 83 Access: Read
>> 84 Valid values: "Unknown", "Critical", "Low", "Normal", "High",
>> 85 "Full"
316 86
317 Valid values: 0 - 100 (percent !! 87 What: /sys/class/power_supply/<supply_name>/current_avg
>> 88 Date: May 2007
>> 89 Contact: linux-pm@vger.kernel.org
>> 90 Description:
>> 91 Reports an average IBAT current reading for the battery, over a
>> 92 fixed period. Normally devices will provide a fixed interval in
>> 93 which they average readings to smooth out the reported value.
318 94
319 What: /sys/class/power_supply/<suppl !! 95 Access: Read
320 Date: June 2009 !! 96 Valid values: Represented in microamps
>> 97
>> 98 What: /sys/class/power_supply/<supply_name>/current_max
>> 99 Date: October 2010
321 Contact: linux-pm@vger.kernel.org 100 Contact: linux-pm@vger.kernel.org
322 Description: 101 Description:
323 Coarse representation of batte !! 102 Reports the maximum IBAT current allowed into the battery.
324 103
325 Access: Read 104 Access: Read
>> 105 Valid values: Represented in microamps
326 106
327 Valid values: !! 107 What: /sys/class/power_supply/<supply_name>/current_now
328 "Unknown", "Crit !! 108 Date: May 2007
329 "Full" !! 109 Contact: linux-pm@vger.kernel.org
>> 110 Description:
>> 111 Reports an instant, single IBAT current reading for the battery.
>> 112 This value is not averaged/smoothed.
>> 113
>> 114 Access: Read
>> 115 Valid values: Represented in microamps
330 116
331 What: /sys/class/power_supply/<suppl 117 What: /sys/class/power_supply/<supply_name>/charge_control_limit
332 Date: Oct 2012 118 Date: Oct 2012
333 Contact: linux-pm@vger.kernel.org 119 Contact: linux-pm@vger.kernel.org
334 Description: 120 Description:
335 Maximum allowable charging cur 121 Maximum allowable charging current. Used for charge rate
336 throttling for thermal cooling 122 throttling for thermal cooling or improving battery health.
337 123
338 Access: Read, Write 124 Access: Read, Write
339 <<
340 Valid values: Represented in m 125 Valid values: Represented in microamps
341 126
342 What: /sys/class/power_supply/<suppl 127 What: /sys/class/power_supply/<supply_name>/charge_control_limit_max
343 Date: Oct 2012 128 Date: Oct 2012
344 Contact: linux-pm@vger.kernel.org 129 Contact: linux-pm@vger.kernel.org
345 Description: 130 Description:
346 Maximum legal value for the ch 131 Maximum legal value for the charge_control_limit property.
347 132
348 Access: Read 133 Access: Read
349 <<
350 Valid values: Represented in m 134 Valid values: Represented in microamps
351 135
352 What: /sys/class/power_supply/<suppl 136 What: /sys/class/power_supply/<supply_name>/charge_control_start_threshold
353 Date: April 2019 137 Date: April 2019
354 Contact: linux-pm@vger.kernel.org 138 Contact: linux-pm@vger.kernel.org
355 Description: 139 Description:
356 Represents a battery percentag 140 Represents a battery percentage level, below which charging will
357 begin. 141 begin.
358 142
359 Access: Read, Write 143 Access: Read, Write
360 Valid values: 0 - 100 (percent 144 Valid values: 0 - 100 (percent)
361 145
362 What: /sys/class/power_supply/<suppl 146 What: /sys/class/power_supply/<supply_name>/charge_control_end_threshold
363 Date: April 2019 147 Date: April 2019
364 Contact: linux-pm@vger.kernel.org 148 Contact: linux-pm@vger.kernel.org
365 Description: 149 Description:
366 Represents a battery percentag 150 Represents a battery percentage level, above which charging will
367 stop. Not all hardware is capa !! 151 stop.
368 percentage. Drivers will round <<
369 supported value. Reading back <<
370 threshold set by the driver. <<
371 152
372 Access: Read, Write 153 Access: Read, Write
373 <<
374 Valid values: 0 - 100 (percent 154 Valid values: 0 - 100 (percent)
375 155
376 What: /sys/class/power_supply/<suppl 156 What: /sys/class/power_supply/<supply_name>/charge_type
377 Date: July 2009 157 Date: July 2009
378 Contact: linux-pm@vger.kernel.org 158 Contact: linux-pm@vger.kernel.org
379 Description: 159 Description:
380 Select the charging algorithm !! 160 Represents the type of charging currently being applied to the
381 !! 161 battery. "Trickle", "Fast", and "Standard" all mean different
382 Standard: !! 162 charging speeds. "Adaptive" means that the charger uses some
383 Fully charge the batte !! 163 algorithm to adjust the charge rate dynamically, without
384 Fast: !! 164 any user configuration required. "Custom" means that the charger
385 Quickly charge the bat !! 165 uses the charge_control_* properties as configuration for some
386 technology. This is ty !! 166 different algorithm.
387 than standard charging <<
388 Trickle: <<
389 Users who primarily op <<
390 plugged into an extern <<
391 battery life with this <<
392 call this "Primarily A <<
393 Adaptive: <<
394 Automatically optimize <<
395 on typical usage patte <<
396 Custom: <<
397 Use the charge_control <<
398 when to start and stop <<
399 can use this to drasti <<
400 Long Life: <<
401 The charger reduces it <<
402 prolong the battery he <<
403 Bypass: <<
404 The charger bypasses t <<
405 integrated converter a <<
406 adaptor to perform the <<
407 167
408 Access: Read, Write 168 Access: Read, Write
409 !! 169 Valid values: "Unknown", "N/A", "Trickle", "Fast", "Standard",
410 Valid values: !! 170 "Adaptive", "Custom"
411 "Unknown", "N/A" <<
412 "Adaptive", "Cus <<
413 171
414 What: /sys/class/power_supply/<suppl 172 What: /sys/class/power_supply/<supply_name>/charge_term_current
415 Date: July 2014 173 Date: July 2014
416 Contact: linux-pm@vger.kernel.org 174 Contact: linux-pm@vger.kernel.org
417 Description: 175 Description:
418 Reports the charging current v 176 Reports the charging current value which is used to determine
419 when the battery is considered 177 when the battery is considered full and charging should end.
420 178
421 Access: Read 179 Access: Read
422 <<
423 Valid values: Represented in m 180 Valid values: Represented in microamps
424 181
425 What: /sys/class/power_supply/<suppl 182 What: /sys/class/power_supply/<supply_name>/health
426 Date: May 2007 183 Date: May 2007
427 Contact: linux-pm@vger.kernel.org 184 Contact: linux-pm@vger.kernel.org
428 Description: 185 Description:
429 Reports the health of the batt 186 Reports the health of the battery or battery side of charger
430 functionality. 187 functionality.
431 188
432 Access: Read 189 Access: Read
433 !! 190 Valid values: "Unknown", "Good", "Overheat", "Dead",
434 Valid values: <<
435 "Unknown", "Good <<
436 "Over voltage", 191 "Over voltage", "Unspecified failure", "Cold",
437 "Watchdog timer 192 "Watchdog timer expire", "Safety timer expire",
438 "Over current", !! 193 "Over current"
439 "Cool", "Hot", " <<
440 194
441 What: /sys/class/power_supply/<suppl 195 What: /sys/class/power_supply/<supply_name>/precharge_current
442 Date: June 2017 196 Date: June 2017
443 Contact: linux-pm@vger.kernel.org 197 Contact: linux-pm@vger.kernel.org
444 Description: 198 Description:
445 Reports the charging current a 199 Reports the charging current applied during pre-charging phase
446 for a battery charge cycle. 200 for a battery charge cycle.
447 201
448 Access: Read 202 Access: Read
449 <<
450 Valid values: Represented in m 203 Valid values: Represented in microamps
451 204
452 What: /sys/class/power_supply/<suppl 205 What: /sys/class/power_supply/<supply_name>/present
453 Date: May 2007 206 Date: May 2007
454 Contact: linux-pm@vger.kernel.org 207 Contact: linux-pm@vger.kernel.org
455 Description: 208 Description:
456 Reports whether a battery is p !! 209 Reports whether a battery is present or not in the system.
457 property does not exist, the b <<
458 210
459 Access: Read 211 Access: Read
460 <<
461 Valid values: 212 Valid values:
462 <<
463 == ======= <<
464 0: Absent 213 0: Absent
465 1: Present 214 1: Present
466 == ======= <<
467 215
468 What: /sys/class/power_supply/<suppl 216 What: /sys/class/power_supply/<supply_name>/status
469 Date: May 2007 217 Date: May 2007
470 Contact: linux-pm@vger.kernel.org 218 Contact: linux-pm@vger.kernel.org
471 Description: 219 Description:
472 Represents the charging status 220 Represents the charging status of the battery. Normally this
473 is read-only reporting althoug 221 is read-only reporting although for some supplies this can be
474 used to enable/disable chargin 222 used to enable/disable charging to the battery.
475 223
476 Access: Read, Write 224 Access: Read, Write
477 !! 225 Valid values: "Unknown", "Charging", "Discharging",
478 Valid values: <<
479 "Unknown", "Char <<
480 "Not charging", 226 "Not charging", "Full"
481 227
482 What: /sys/class/power_supply/<suppl !! 228 What: /sys/class/power_supply/<supply_name>/technology
483 Date: November 2021 !! 229 Date: May 2007
484 Contact: linux-pm@vger.kernel.org 230 Contact: linux-pm@vger.kernel.org
485 Description: 231 Description:
486 Represents the charging behavi !! 232 Describes the battery technology supported by the supply.
487 <<
488 Access: Read, Write <<
489 233
490 Valid values: !! 234 Access: Read
491 ================ ===== !! 235 Valid values: "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
492 auto: Charg !! 236 "NiCd", "LiMn"
493 inhibit-charge: Do no <<
494 force-discharge: Force <<
495 ================ ===== <<
496 237
497 What: /sys/class/power_supply/<suppl !! 238 What: /sys/class/power_supply/<supply_name>/temp
498 Date: May 2007 239 Date: May 2007
499 Contact: linux-pm@vger.kernel.org 240 Contact: linux-pm@vger.kernel.org
500 Description: 241 Description:
501 Describes the battery technolo !! 242 Reports the current TBAT battery temperature reading.
502 243
503 Access: Read 244 Access: Read
>> 245 Valid values: Represented in 1/10 Degrees Celsius
504 246
505 Valid values: !! 247 What: /sys/class/power_supply/<supply_name>/temp_alert_max
506 "Unknown", "NiMH !! 248 Date: July 2012
507 "NiCd", "LiMn" !! 249 Contact: linux-pm@vger.kernel.org
>> 250 Description:
>> 251 Maximum TBAT temperature trip-wire value where the supply will
>> 252 notify user-space of the event. This is normally used for the
>> 253 battery charging scenario where user-space needs to know the
>> 254 battery temperature has crossed an upper threshold so it can
>> 255 take appropriate action (e.g. warning user that battery level is
>> 256 critically high, and charging has stopped).
>> 257
>> 258 Access: Read
>> 259 Valid values: Represented in 1/10 Degrees Celsius
>> 260
>> 261 What: /sys/class/power_supply/<supply_name>/temp_alert_min
>> 262 Date: July 2012
>> 263 Contact: linux-pm@vger.kernel.org
>> 264 Description:
>> 265 Minimum TBAT temperature trip-wire value where the supply will
>> 266 notify user-space of the event. This is normally used for the
>> 267 battery charging scenario where user-space needs to know the
>> 268 battery temperature has crossed a lower threshold so it can take
>> 269 appropriate action (e.g. warning user that battery level is
>> 270 high, and charging current has been reduced accordingly to
>> 271 remedy the situation).
>> 272
>> 273 Access: Read
>> 274 Valid values: Represented in 1/10 Degrees Celsius
508 275
>> 276 What: /sys/class/power_supply/<supply_name>/temp_max
>> 277 Date: July 2014
>> 278 Contact: linux-pm@vger.kernel.org
>> 279 Description:
>> 280 Reports the maximum allowed TBAT battery temperature for
>> 281 charging.
>> 282
>> 283 Access: Read
>> 284 Valid values: Represented in 1/10 Degrees Celsius
>> 285
>> 286 What: /sys/class/power_supply/<supply_name>/temp_min
>> 287 Date: July 2014
>> 288 Contact: linux-pm@vger.kernel.org
>> 289 Description:
>> 290 Reports the minimum allowed TBAT battery temperature for
>> 291 charging.
>> 292
>> 293 Access: Read
>> 294 Valid values: Represented in 1/10 Degrees Celsius
509 295
510 What: /sys/class/power_supply/<suppl 296 What: /sys/class/power_supply/<supply_name>/voltage_avg,
511 Date: May 2007 297 Date: May 2007
512 Contact: linux-pm@vger.kernel.org 298 Contact: linux-pm@vger.kernel.org
513 Description: 299 Description:
514 Reports an average VBAT voltag 300 Reports an average VBAT voltage reading for the battery, over a
515 fixed period. Normally devices 301 fixed period. Normally devices will provide a fixed interval in
516 which they average readings to 302 which they average readings to smooth out the reported value.
517 303
518 Access: Read 304 Access: Read
>> 305 Valid values: Represented in microvolts
>> 306
>> 307 What: /sys/class/power_supply/<supply_name>/voltage_max,
>> 308 Date: January 2008
>> 309 Contact: linux-pm@vger.kernel.org
>> 310 Description:
>> 311 Reports the maximum safe VBAT voltage permitted for the battery,
>> 312 during charging.
519 313
>> 314 Access: Read
520 Valid values: Represented in m 315 Valid values: Represented in microvolts
521 316
522 What: /sys/class/power_supply/<suppl !! 317 What: /sys/class/power_supply/<supply_name>/voltage_min,
523 Date: January 2010 !! 318 Date: January 2008
524 Contact: linux-pm@vger.kernel.org 319 Contact: linux-pm@vger.kernel.org
525 Description: 320 Description:
526 Reports the number of full cha !! 321 Reports the minimum safe VBAT voltage permitted for the battery,
527 battery has undergone. !! 322 during discharging.
528 323
529 Access: Read 324 Access: Read
>> 325 Valid values: Represented in microvolts
530 326
531 Valid values: !! 327 What: /sys/class/power_supply/<supply_name>/voltage_now,
532 Integer > 0: represent !! 328 Date: May 2007
533 Integer = 0: cycle_cou !! 329 Contact: linux-pm@vger.kernel.org
>> 330 Description:
>> 331 Reports an instant, single VBAT voltage reading for the battery.
>> 332 This value is not averaged/smoothed.
>> 333
>> 334 Access: Read
>> 335 Valid values: Represented in microvolts
534 336
535 **USB Properties** !! 337 ===== USB Properties =====
>> 338
>> 339 What: /sys/class/power_supply/<supply_name>/current_avg
>> 340 Date: May 2007
>> 341 Contact: linux-pm@vger.kernel.org
>> 342 Description:
>> 343 Reports an average IBUS current reading over a fixed period.
>> 344 Normally devices will provide a fixed interval in which they
>> 345 average readings to smooth out the reported value.
>> 346
>> 347 Access: Read
>> 348 Valid values: Represented in microamps
>> 349
>> 350
>> 351 What: /sys/class/power_supply/<supply_name>/current_max
>> 352 Date: October 2010
>> 353 Contact: linux-pm@vger.kernel.org
>> 354 Description:
>> 355 Reports the maximum IBUS current the supply can support.
>> 356
>> 357 Access: Read
>> 358 Valid values: Represented in microamps
>> 359
>> 360 What: /sys/class/power_supply/<supply_name>/current_now
>> 361 Date: May 2007
>> 362 Contact: linux-pm@vger.kernel.org
>> 363 Description:
>> 364 Reports the IBUS current supplied now. This value is generally
>> 365 read-only reporting, unless the 'online' state of the supply
>> 366 is set to be programmable, in which case this value can be set
>> 367 within the reported min/max range.
>> 368
>> 369 Access: Read, Write
>> 370 Valid values: Represented in microamps
536 371
537 What: /sys/class/power_supply/<suppl 372 What: /sys/class/power_supply/<supply_name>/input_current_limit
538 Date: July 2014 373 Date: July 2014
539 Contact: linux-pm@vger.kernel.org 374 Contact: linux-pm@vger.kernel.org
540 Description: 375 Description:
541 Details the incoming IBUS curr 376 Details the incoming IBUS current limit currently set in the
542 supply. Normally this is confi 377 supply. Normally this is configured based on the type of
543 connection made (e.g. A config 378 connection made (e.g. A configured SDP should output a maximum
544 of 500mA so the input current 379 of 500mA so the input current limit is set to the same value).
545 Use preferably input_power_lim 380 Use preferably input_power_limit, and for problems that can be
546 solved using power limit use i 381 solved using power limit use input_current_limit.
547 382
548 Access: Read, Write 383 Access: Read, Write
549 <<
550 Valid values: Represented in m 384 Valid values: Represented in microamps
551 385
552 What: /sys/class/power_supply/<suppl 386 What: /sys/class/power_supply/<supply_name>/input_voltage_limit
553 Date: May 2019 387 Date: May 2019
554 Contact: linux-pm@vger.kernel.org 388 Contact: linux-pm@vger.kernel.org
555 Description: 389 Description:
556 This entry configures the inco 390 This entry configures the incoming VBUS voltage limit currently
557 set in the supply. Normally th 391 set in the supply. Normally this is configured based on
558 system-level knowledge or user 392 system-level knowledge or user input (e.g. This is part of the
559 Pixel C's thermal management s 393 Pixel C's thermal management strategy to effectively limit the
560 input power to 5V when the scr 394 input power to 5V when the screen is on to meet Google's skin
561 temperature targets). Note tha 395 temperature targets). Note that this feature should not be
562 used for safety critical thing 396 used for safety critical things.
563 Use preferably input_power_lim 397 Use preferably input_power_limit, and for problems that can be
564 solved using power limit use i 398 solved using power limit use input_voltage_limit.
565 399
566 Access: Read, Write 400 Access: Read, Write
567 <<
568 Valid values: Represented in m 401 Valid values: Represented in microvolts
569 402
570 What: /sys/class/power_supply/<suppl 403 What: /sys/class/power_supply/<supply_name>/input_power_limit
571 Date: May 2019 404 Date: May 2019
572 Contact: linux-pm@vger.kernel.org 405 Contact: linux-pm@vger.kernel.org
573 Description: 406 Description:
574 This entry configures the inco 407 This entry configures the incoming power limit currently set
575 in the supply. Normally this i 408 in the supply. Normally this is configured based on
576 system-level knowledge or user 409 system-level knowledge or user input. Use preferably this
577 feature to limit the incoming 410 feature to limit the incoming power and use current/voltage
578 limit only for problems that c 411 limit only for problems that can be solved using power limit.
579 412
580 Access: Read, Write 413 Access: Read, Write
581 <<
582 Valid values: Represented in m 414 Valid values: Represented in microwatts
583 415
584 What: /sys/class/power_supply/<suppl 416 What: /sys/class/power_supply/<supply_name>/online,
585 Date: May 2007 417 Date: May 2007
586 Contact: linux-pm@vger.kernel.org 418 Contact: linux-pm@vger.kernel.org
587 Description: 419 Description:
588 Indicates if VBUS is present f 420 Indicates if VBUS is present for the supply. When the supply is
589 online, and the supply allows 421 online, and the supply allows it, then it's possible to switch
590 between online states (e.g. Fi 422 between online states (e.g. Fixed -> Programmable for a PD_PPS
591 USB supply so voltage and curr 423 USB supply so voltage and current can be controlled).
592 424
593 Access: Read, Write 425 Access: Read, Write
594 <<
595 Valid values: 426 Valid values:
596 <<
597 == =================== <<
598 0: Offline 427 0: Offline
599 1: Online Fixed - Fixe 428 1: Online Fixed - Fixed Voltage Supply
600 2: Online Programmable 429 2: Online Programmable - Programmable Voltage Supply
601 == =================== !! 430
>> 431 What: /sys/class/power_supply/<supply_name>/temp
>> 432 Date: May 2007
>> 433 Contact: linux-pm@vger.kernel.org
>> 434 Description:
>> 435 Reports the current supply temperature reading. This would
>> 436 normally be the internal temperature of the device itself (e.g
>> 437 TJUNC temperature of an IC)
>> 438
>> 439 Access: Read
>> 440 Valid values: Represented in 1/10 Degrees Celsius
>> 441
>> 442 What: /sys/class/power_supply/<supply_name>/temp_alert_max
>> 443 Date: July 2012
>> 444 Contact: linux-pm@vger.kernel.org
>> 445 Description:
>> 446 Maximum supply temperature trip-wire value where the supply will
>> 447 notify user-space of the event. This is normally used for the
>> 448 charging scenario where user-space needs to know the supply
>> 449 temperature has crossed an upper threshold so it can take
>> 450 appropriate action (e.g. warning user that the supply
>> 451 temperature is critically high, and charging has stopped to
>> 452 remedy the situation).
>> 453
>> 454 Access: Read
>> 455 Valid values: Represented in 1/10 Degrees Celsius
>> 456
>> 457 What: /sys/class/power_supply/<supply_name>/temp_alert_min
>> 458 Date: July 2012
>> 459 Contact: linux-pm@vger.kernel.org
>> 460 Description:
>> 461 Minimum supply temperature trip-wire value where the supply will
>> 462 notify user-space of the event. This is normally used for the
>> 463 charging scenario where user-space needs to know the supply
>> 464 temperature has crossed a lower threshold so it can take
>> 465 appropriate action (e.g. warning user that the supply
>> 466 temperature is high, and charging current has been reduced
>> 467 accordingly to remedy the situation).
>> 468
>> 469 Access: Read
>> 470 Valid values: Represented in 1/10 Degrees Celsius
>> 471
>> 472 What: /sys/class/power_supply/<supply_name>/temp_max
>> 473 Date: July 2014
>> 474 Contact: linux-pm@vger.kernel.org
>> 475 Description:
>> 476 Reports the maximum allowed supply temperature for operation.
>> 477
>> 478 Access: Read
>> 479 Valid values: Represented in 1/10 Degrees Celsius
>> 480
>> 481 What: /sys/class/power_supply/<supply_name>/temp_min
>> 482 Date: July 2014
>> 483 Contact: linux-pm@vger.kernel.org
>> 484 Description:
>> 485 Reports the mainimum allowed supply temperature for operation.
>> 486
>> 487 Access: Read
>> 488 Valid values: Represented in 1/10 Degrees Celsius
602 489
603 What: /sys/class/power_supply/<suppl 490 What: /sys/class/power_supply/<supply_name>/usb_type
604 Date: March 2018 491 Date: March 2018
605 Contact: linux-pm@vger.kernel.org 492 Contact: linux-pm@vger.kernel.org
606 Description: 493 Description:
607 Reports what type of USB conne 494 Reports what type of USB connection is currently active for
608 the supply, for example it can 495 the supply, for example it can show if USB-PD capable source
609 is attached. 496 is attached.
610 497
611 Access: For power-supplies whi !! 498 Access: Read-Only
612 as battery charger chips, this !! 499 Valid values: "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
613 the connected USB power source !! 500 "PD_DRP", "PD_PPS", "BrickID"
>> 501
>> 502 What: /sys/class/power_supply/<supply_name>/voltage_max
>> 503 Date: January 2008
>> 504 Contact: linux-pm@vger.kernel.org
>> 505 Description:
>> 506 Reports the maximum VBUS voltage the supply can support.
614 507
615 For power-supplies which act a !! 508 Access: Read
616 e.g. the UCS1002 USB Port Powe !! 509 Valid values: Represented in microvolts
617 510
618 Valid values: !! 511 What: /sys/class/power_supply/<supply_name>/voltage_min
619 "Unknown", "SDP" !! 512 Date: January 2008
620 "PD_DRP", "PD_PP !! 513 Contact: linux-pm@vger.kernel.org
>> 514 Description:
>> 515 Reports the minimum VBUS voltage the supply can support.
621 516
622 **Device Specific Properties** !! 517 Access: Read
>> 518 Valid values: Represented in microvolts
>> 519
>> 520 What: /sys/class/power_supply/<supply_name>/voltage_now
>> 521 Date: May 2007
>> 522 Contact: linux-pm@vger.kernel.org
>> 523 Description:
>> 524 Reports the VBUS voltage supplied now. This value is generally
>> 525 read-only reporting, unless the 'online' state of the supply
>> 526 is set to be programmable, in which case this value can be set
>> 527 within the reported min/max range.
>> 528
>> 529 Access: Read, Write
>> 530 Valid values: Represented in microvolts
>> 531
>> 532 ===== Device Specific Properties =====
623 533
624 What: /sys/class/power/ds2760-batter 534 What: /sys/class/power/ds2760-battery.*/charge_now
625 Date: May 2010 535 Date: May 2010
626 KernelVersion: 2.6.35 536 KernelVersion: 2.6.35
627 Contact: Daniel Mack <daniel@caiaq.de> 537 Contact: Daniel Mack <daniel@caiaq.de>
628 Description: 538 Description:
629 This file is writeable and can 539 This file is writeable and can be used to set the current
630 coloumb counter value inside t 540 coloumb counter value inside the battery monitor chip. This
631 is needed for unavoidable corr 541 is needed for unavoidable corrections of aging batteries.
632 A userspace daemon can monitor 542 A userspace daemon can monitor the battery charging logic
633 and once the counter drops out 543 and once the counter drops out of considerable bounds, take
634 appropriate action. 544 appropriate action.
635 545
636 What: /sys/class/power/ds2760-batter 546 What: /sys/class/power/ds2760-battery.*/charge_full
637 Date: May 2010 547 Date: May 2010
638 KernelVersion: 2.6.35 548 KernelVersion: 2.6.35
639 Contact: Daniel Mack <daniel@caiaq.de> 549 Contact: Daniel Mack <daniel@caiaq.de>
640 Description: 550 Description:
641 This file is writeable and can 551 This file is writeable and can be used to set the assumed
642 battery 'full level'. As batte 552 battery 'full level'. As batteries age, this value has to be
643 amended over time. 553 amended over time.
644 554
645 What: /sys/class/power_supply/max145 555 What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
646 Date: October 2014 556 Date: October 2014
647 KernelVersion: 3.18.0 557 KernelVersion: 3.18.0
648 Contact: Krzysztof Kozlowski <krzk@kerne 558 Contact: Krzysztof Kozlowski <krzk@kernel.org>
649 Description: 559 Description:
650 This entry shows and sets the 560 This entry shows and sets the maximum time the max14577
651 charger operates in fast-charg 561 charger operates in fast-charge mode. When the timer expires
652 the device will terminate fast 562 the device will terminate fast-charge mode (charging current
653 will drop to 0 A) and will tri 563 will drop to 0 A) and will trigger interrupt.
654 564
655 Valid values: 565 Valid values:
656 <<
657 - 5, 6 or 7 (hours), 566 - 5, 6 or 7 (hours),
658 - 0: disabled. 567 - 0: disabled.
659 568
660 What: /sys/class/power_supply/max776 569 What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer
661 Date: January 2015 570 Date: January 2015
662 KernelVersion: 3.19.0 571 KernelVersion: 3.19.0
663 Contact: Krzysztof Kozlowski <krzk@kerne 572 Contact: Krzysztof Kozlowski <krzk@kernel.org>
664 Description: 573 Description:
665 This entry shows and sets the 574 This entry shows and sets the maximum time the max77693
666 charger operates in fast-charg 575 charger operates in fast-charge mode. When the timer expires
667 the device will terminate fast 576 the device will terminate fast-charge mode (charging current
668 will drop to 0 A) and will tri 577 will drop to 0 A) and will trigger interrupt.
669 578
670 Valid values: 579 Valid values:
671 <<
672 - 4 - 16 (hours), step by 2 (r 580 - 4 - 16 (hours), step by 2 (rounded down)
673 - 0: disabled. 581 - 0: disabled.
674 582
675 What: /sys/class/power_supply/max776 583 What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
676 Date: January 2015 584 Date: January 2015
677 KernelVersion: 3.19.0 585 KernelVersion: 3.19.0
678 Contact: Krzysztof Kozlowski <krzk@kerne 586 Contact: Krzysztof Kozlowski <krzk@kernel.org>
679 Description: 587 Description:
680 This entry shows and sets the 588 This entry shows and sets the charging current threshold for
681 entering top-off charging mode 589 entering top-off charging mode. When charging current in fast
682 charge mode drops below this v 590 charge mode drops below this value, the charger will trigger
683 interrupt and start top-off ch 591 interrupt and start top-off charging mode.
684 592
685 Valid values: 593 Valid values:
686 <<
687 - 100000 - 200000 (microamps), 594 - 100000 - 200000 (microamps), step by 25000 (rounded down)
688 - 200000 - 350000 (microamps), 595 - 200000 - 350000 (microamps), step by 50000 (rounded down)
689 - 0: disabled. 596 - 0: disabled.
690 597
691 What: /sys/class/power_supply/max776 598 What: /sys/class/power_supply/max77693-charger/device/top_off_timer
692 Date: January 2015 599 Date: January 2015
693 KernelVersion: 3.19.0 600 KernelVersion: 3.19.0
694 Contact: Krzysztof Kozlowski <krzk@kerne 601 Contact: Krzysztof Kozlowski <krzk@kernel.org>
695 Description: 602 Description:
696 This entry shows and sets the 603 This entry shows and sets the maximum time the max77693
697 charger operates in top-off ch 604 charger operates in top-off charge mode. When the timer expires
698 the device will terminate top- 605 the device will terminate top-off charge mode (charging current
699 will drop to 0 A) and will tri 606 will drop to 0 A) and will trigger interrupt.
700 607
701 Valid values: 608 Valid values:
702 <<
703 - 0 - 70 (minutes), step by 10 609 - 0 - 70 (minutes), step by 10 (rounded down)
704 610
705 What: /sys/class/power_supply/bq2425 611 What: /sys/class/power_supply/bq24257-charger/ovp_voltage
706 Date: October 2015 612 Date: October 2015
707 KernelVersion: 4.4.0 613 KernelVersion: 4.4.0
708 Contact: Andreas Dannenberg <dannenberg@ 614 Contact: Andreas Dannenberg <dannenberg@ti.com>
709 Description: 615 Description:
710 This entry configures the over 616 This entry configures the overvoltage protection feature of bq24257-
711 type charger devices. This fea 617 type charger devices. This feature protects the device and other
712 components against damage from 618 components against damage from overvoltage on the input supply. See
713 device datasheet for details. 619 device datasheet for details.
714 620
715 Valid values: 621 Valid values:
716 <<
717 - 6000000, 6500000, 7000000, 8 622 - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
718 10500000 (all uV) 623 10500000 (all uV)
719 624
720 What: /sys/class/power_supply/bq2425 625 What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage
721 Date: October 2015 626 Date: October 2015
722 KernelVersion: 4.4.0 627 KernelVersion: 4.4.0
723 Contact: Andreas Dannenberg <dannenberg@ 628 Contact: Andreas Dannenberg <dannenberg@ti.com>
724 Description: 629 Description:
725 This entry configures the inpu 630 This entry configures the input dynamic power path management voltage of
726 bq24257-type charger devices. 631 bq24257-type charger devices. Once the supply drops to the configured
727 voltage, the input current lim 632 voltage, the input current limit is reduced down to prevent the further
728 drop of the supply. When the I 633 drop of the supply. When the IC enters this mode, the charge current is
729 lower than the set value. See 634 lower than the set value. See device datasheet for details.
730 635
731 Valid values: 636 Valid values:
732 <<
733 - 4200000, 4280000, 4360000, 4 637 - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
734 4760000 (all uV) 638 4760000 (all uV)
735 639
736 What: /sys/class/power_supply/bq2425 640 What: /sys/class/power_supply/bq24257-charger/high_impedance_enable
737 Date: October 2015 641 Date: October 2015
738 KernelVersion: 4.4.0 642 KernelVersion: 4.4.0
739 Contact: Andreas Dannenberg <dannenberg@ 643 Contact: Andreas Dannenberg <dannenberg@ti.com>
740 Description: 644 Description:
741 This entry allows enabling the 645 This entry allows enabling the high-impedance mode of bq24257-type
742 charger devices. If enabled, i 646 charger devices. If enabled, it places the charger IC into low power
743 standby mode with the switch m 647 standby mode with the switch mode controller disabled. When disabled,
744 the charger operates normally. 648 the charger operates normally. See device datasheet for details.
745 649
746 Valid values: 650 Valid values:
747 <<
748 - 1: enabled 651 - 1: enabled
749 - 0: disabled 652 - 0: disabled
750 653
751 What: /sys/class/power_supply/bq2425 654 What: /sys/class/power_supply/bq24257-charger/sysoff_enable
752 Date: October 2015 655 Date: October 2015
753 KernelVersion: 4.4.0 656 KernelVersion: 4.4.0
754 Contact: Andreas Dannenberg <dannenberg@ 657 Contact: Andreas Dannenberg <dannenberg@ti.com>
755 Description: 658 Description:
756 This entry allows enabling the 659 This entry allows enabling the sysoff mode of bq24257-type charger
757 devices. If enabled and the in 660 devices. If enabled and the input is removed, the internal battery FET
758 is turned off in order to redu 661 is turned off in order to reduce the leakage from the BAT pin to less
759 than 1uA. Note that on some de 662 than 1uA. Note that on some devices/systems this disconnects the battery
760 from the system. See device da 663 from the system. See device datasheet for details.
761 664
762 Valid values: 665 Valid values:
763 <<
764 - 1: enabled 666 - 1: enabled
765 - 0: disabled 667 - 0: disabled
766 <<
767 What: /sys/class/power_supply/<suppl <<
768 Date: January 2020 <<
769 Contact: linux-pm@vger.kernel.org <<
770 Description: <<
771 Reports the year (following Gr <<
772 manufactured. <<
773 <<
774 Access: Read <<
775 <<
776 Valid values: Reported as inte <<
777 <<
778 What: /sys/class/power_supply/<suppl <<
779 Date: January 2020 <<
780 Contact: linux-pm@vger.kernel.org <<
781 Description: <<
782 Reports the month when the dev <<
783 <<
784 Access: Read <<
785 <<
786 Valid values: 1-12 <<
787 <<
788 What: /sys/class/power_supply/<suppl <<
789 Date: January 2020 <<
790 Contact: linux-pm@vger.kernel.org <<
791 Description: <<
792 Reports the day of month when <<
793 <<
794 Access: Read <<
795 Valid values: 1-31 <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.