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", <<
439 "Cool", "Hot", " <<
440 193
441 What: /sys/class/power_supply/<suppl 194 What: /sys/class/power_supply/<supply_name>/precharge_current
442 Date: June 2017 195 Date: June 2017
443 Contact: linux-pm@vger.kernel.org 196 Contact: linux-pm@vger.kernel.org
444 Description: 197 Description:
445 Reports the charging current a 198 Reports the charging current applied during pre-charging phase
446 for a battery charge cycle. 199 for a battery charge cycle.
447 200
448 Access: Read 201 Access: Read
449 <<
450 Valid values: Represented in m 202 Valid values: Represented in microamps
451 203
452 What: /sys/class/power_supply/<suppl 204 What: /sys/class/power_supply/<supply_name>/present
453 Date: May 2007 205 Date: May 2007
454 Contact: linux-pm@vger.kernel.org 206 Contact: linux-pm@vger.kernel.org
455 Description: 207 Description:
456 Reports whether a battery is p !! 208 Reports whether a battery is present or not in the system.
457 property does not exist, the b <<
458 209
459 Access: Read 210 Access: Read
460 <<
461 Valid values: 211 Valid values:
462 <<
463 == ======= <<
464 0: Absent 212 0: Absent
465 1: Present 213 1: Present
466 == ======= <<
467 214
468 What: /sys/class/power_supply/<suppl 215 What: /sys/class/power_supply/<supply_name>/status
469 Date: May 2007 216 Date: May 2007
470 Contact: linux-pm@vger.kernel.org 217 Contact: linux-pm@vger.kernel.org
471 Description: 218 Description:
472 Represents the charging status 219 Represents the charging status of the battery. Normally this
473 is read-only reporting althoug 220 is read-only reporting although for some supplies this can be
474 used to enable/disable chargin 221 used to enable/disable charging to the battery.
475 222
476 Access: Read, Write 223 Access: Read, Write
477 !! 224 Valid values: "Unknown", "Charging", "Discharging",
478 Valid values: <<
479 "Unknown", "Char <<
480 "Not charging", 225 "Not charging", "Full"
481 226
482 What: /sys/class/power_supply/<suppl !! 227 What: /sys/class/power_supply/<supply_name>/technology
483 Date: November 2021 !! 228 Date: May 2007
>> 229 Contact: linux-pm@vger.kernel.org
>> 230 Description:
>> 231 Describes the battery technology supported by the supply.
>> 232
>> 233 Access: Read
>> 234 Valid values: "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
>> 235 "NiCd", "LiMn"
>> 236
>> 237 What: /sys/class/power_supply/<supply_name>/temp
>> 238 Date: May 2007
484 Contact: linux-pm@vger.kernel.org 239 Contact: linux-pm@vger.kernel.org
485 Description: 240 Description:
486 Represents the charging behavi !! 241 Reports the current TBAT battery temperature reading.
487 242
488 Access: Read, Write !! 243 Access: Read
>> 244 Valid values: Represented in 1/10 Degrees Celsius
489 245
490 Valid values: !! 246 What: /sys/class/power_supply/<supply_name>/temp_alert_max
491 ================ ===== !! 247 Date: July 2012
492 auto: Charg !! 248 Contact: linux-pm@vger.kernel.org
493 inhibit-charge: Do no !! 249 Description:
494 force-discharge: Force !! 250 Maximum TBAT temperature trip-wire value where the supply will
495 ================ ===== !! 251 notify user-space of the event. This is normally used for the
>> 252 battery charging scenario where user-space needs to know the
>> 253 battery temperature has crossed an upper threshold so it can
>> 254 take appropriate action (e.g. warning user that battery level is
>> 255 critically high, and charging has stopped).
496 256
497 What: /sys/class/power_supply/<suppl !! 257 Access: Read
498 Date: May 2007 !! 258 Valid values: Represented in 1/10 Degrees Celsius
>> 259
>> 260 What: /sys/class/power_supply/<supply_name>/temp_alert_min
>> 261 Date: July 2012
499 Contact: linux-pm@vger.kernel.org 262 Contact: linux-pm@vger.kernel.org
500 Description: 263 Description:
501 Describes the battery technolo !! 264 Minimum TBAT temperature trip-wire value where the supply will
>> 265 notify user-space of the event. This is normally used for the
>> 266 battery charging scenario where user-space needs to know the
>> 267 battery temperature has crossed a lower threshold so it can take
>> 268 appropriate action (e.g. warning user that battery level is
>> 269 high, and charging current has been reduced accordingly to
>> 270 remedy the situation).
502 271
503 Access: Read 272 Access: Read
>> 273 Valid values: Represented in 1/10 Degrees Celsius
504 274
505 Valid values: !! 275 What: /sys/class/power_supply/<supply_name>/temp_max
506 "Unknown", "NiMH !! 276 Date: July 2014
507 "NiCd", "LiMn" !! 277 Contact: linux-pm@vger.kernel.org
>> 278 Description:
>> 279 Reports the maximum allowed TBAT battery temperature for
>> 280 charging.
508 281
>> 282 Access: Read
>> 283 Valid values: Represented in 1/10 Degrees Celsius
>> 284
>> 285 What: /sys/class/power_supply/<supply_name>/temp_min
>> 286 Date: July 2014
>> 287 Contact: linux-pm@vger.kernel.org
>> 288 Description:
>> 289 Reports the minimum allowed TBAT battery temperature for
>> 290 charging.
>> 291
>> 292 Access: Read
>> 293 Valid values: Represented in 1/10 Degrees Celsius
509 294
510 What: /sys/class/power_supply/<suppl 295 What: /sys/class/power_supply/<supply_name>/voltage_avg,
511 Date: May 2007 296 Date: May 2007
512 Contact: linux-pm@vger.kernel.org 297 Contact: linux-pm@vger.kernel.org
513 Description: 298 Description:
514 Reports an average VBAT voltag 299 Reports an average VBAT voltage reading for the battery, over a
515 fixed period. Normally devices 300 fixed period. Normally devices will provide a fixed interval in
516 which they average readings to 301 which they average readings to smooth out the reported value.
517 302
518 Access: Read 303 Access: Read
>> 304 Valid values: Represented in microvolts
519 305
>> 306 What: /sys/class/power_supply/<supply_name>/voltage_max,
>> 307 Date: January 2008
>> 308 Contact: linux-pm@vger.kernel.org
>> 309 Description:
>> 310 Reports the maximum safe VBAT voltage permitted for the battery,
>> 311 during charging.
>> 312
>> 313 Access: Read
520 Valid values: Represented in m 314 Valid values: Represented in microvolts
521 315
522 What: /sys/class/power_supply/<suppl !! 316 What: /sys/class/power_supply/<supply_name>/voltage_min,
523 Date: January 2010 !! 317 Date: January 2008
524 Contact: linux-pm@vger.kernel.org 318 Contact: linux-pm@vger.kernel.org
525 Description: 319 Description:
526 Reports the number of full cha !! 320 Reports the minimum safe VBAT voltage permitted for the battery,
527 battery has undergone. !! 321 during discharging.
528 322
529 Access: Read 323 Access: Read
>> 324 Valid values: Represented in microvolts
530 325
531 Valid values: !! 326 What: /sys/class/power_supply/<supply_name>/voltage_now,
532 Integer > 0: represent !! 327 Date: May 2007
533 Integer = 0: cycle_cou !! 328 Contact: linux-pm@vger.kernel.org
>> 329 Description:
>> 330 Reports an instant, single VBAT voltage reading for the battery.
>> 331 This value is not averaged/smoothed.
534 332
535 **USB Properties** !! 333 Access: Read
>> 334 Valid values: Represented in microvolts
536 335
537 What: /sys/class/power_supply/<suppl !! 336 ===== USB Properties =====
538 Date: July 2014 !! 337
>> 338 What: /sys/class/power_supply/<supply_name>/current_avg
>> 339 Date: May 2007
539 Contact: linux-pm@vger.kernel.org 340 Contact: linux-pm@vger.kernel.org
540 Description: 341 Description:
541 Details the incoming IBUS curr !! 342 Reports an average IBUS current reading over a fixed period.
542 supply. Normally this is confi !! 343 Normally devices will provide a fixed interval in which they
543 connection made (e.g. A config !! 344 average readings to smooth out the reported value.
544 of 500mA so the input current <<
545 Use preferably input_power_lim <<
546 solved using power limit use i <<
547 345
548 Access: Read, Write !! 346 Access: Read
>> 347 Valid values: Represented in microamps
>> 348
>> 349
>> 350 What: /sys/class/power_supply/<supply_name>/current_max
>> 351 Date: October 2010
>> 352 Contact: linux-pm@vger.kernel.org
>> 353 Description:
>> 354 Reports the maximum IBUS current the supply can support.
549 355
>> 356 Access: Read
550 Valid values: Represented in m 357 Valid values: Represented in microamps
551 358
552 What: /sys/class/power_supply/<suppl !! 359 What: /sys/class/power_supply/<supply_name>/current_now
553 Date: May 2019 !! 360 Date: May 2007
554 Contact: linux-pm@vger.kernel.org 361 Contact: linux-pm@vger.kernel.org
555 Description: 362 Description:
556 This entry configures the inco !! 363 Reports the IBUS current supplied now. This value is generally
557 set in the supply. Normally th !! 364 read-only reporting, unless the 'online' state of the supply
558 system-level knowledge or user !! 365 is set to be programmable, in which case this value can be set
559 Pixel C's thermal management s !! 366 within the reported min/max range.
560 input power to 5V when the scr <<
561 temperature targets). Note tha <<
562 used for safety critical thing <<
563 Use preferably input_power_lim <<
564 solved using power limit use i <<
565 367
566 Access: Read, Write 368 Access: Read, Write
>> 369 Valid values: Represented in microamps
567 370
568 Valid values: Represented in m !! 371 What: /sys/class/power_supply/<supply_name>/input_current_limit
569 !! 372 Date: July 2014
570 What: /sys/class/power_supply/<suppl <<
571 Date: May 2019 <<
572 Contact: linux-pm@vger.kernel.org 373 Contact: linux-pm@vger.kernel.org
573 Description: 374 Description:
574 This entry configures the inco !! 375 Details the incoming IBUS current limit currently set in the
575 in the supply. Normally this i !! 376 supply. Normally this is configured based on the type of
576 system-level knowledge or user !! 377 connection made (e.g. A configured SDP should output a maximum
577 feature to limit the incoming !! 378 of 500mA so the input current limit is set to the same value).
578 limit only for problems that c <<
579 379
580 Access: Read, Write 380 Access: Read, Write
581 !! 381 Valid values: Represented in microamps
582 Valid values: Represented in m <<
583 382
584 What: /sys/class/power_supply/<suppl 383 What: /sys/class/power_supply/<supply_name>/online,
585 Date: May 2007 384 Date: May 2007
586 Contact: linux-pm@vger.kernel.org 385 Contact: linux-pm@vger.kernel.org
587 Description: 386 Description:
588 Indicates if VBUS is present f 387 Indicates if VBUS is present for the supply. When the supply is
589 online, and the supply allows 388 online, and the supply allows it, then it's possible to switch
590 between online states (e.g. Fi 389 between online states (e.g. Fixed -> Programmable for a PD_PPS
591 USB supply so voltage and curr 390 USB supply so voltage and current can be controlled).
592 391
593 Access: Read, Write 392 Access: Read, Write
594 <<
595 Valid values: 393 Valid values:
596 <<
597 == =================== <<
598 0: Offline 394 0: Offline
599 1: Online Fixed - Fixe 395 1: Online Fixed - Fixed Voltage Supply
600 2: Online Programmable 396 2: Online Programmable - Programmable Voltage Supply
601 == =================== !! 397
>> 398 What: /sys/class/power_supply/<supply_name>/temp
>> 399 Date: May 2007
>> 400 Contact: linux-pm@vger.kernel.org
>> 401 Description:
>> 402 Reports the current supply temperature reading. This would
>> 403 normally be the internal temperature of the device itself (e.g
>> 404 TJUNC temperature of an IC)
>> 405
>> 406 Access: Read
>> 407 Valid values: Represented in 1/10 Degrees Celsius
>> 408
>> 409 What: /sys/class/power_supply/<supply_name>/temp_alert_max
>> 410 Date: July 2012
>> 411 Contact: linux-pm@vger.kernel.org
>> 412 Description:
>> 413 Maximum supply temperature trip-wire value where the supply will
>> 414 notify user-space of the event. This is normally used for the
>> 415 charging scenario where user-space needs to know the supply
>> 416 temperature has crossed an upper threshold so it can take
>> 417 appropriate action (e.g. warning user that the supply
>> 418 temperature is critically high, and charging has stopped to
>> 419 remedy the situation).
>> 420
>> 421 Access: Read
>> 422 Valid values: Represented in 1/10 Degrees Celsius
>> 423
>> 424 What: /sys/class/power_supply/<supply_name>/temp_alert_min
>> 425 Date: July 2012
>> 426 Contact: linux-pm@vger.kernel.org
>> 427 Description:
>> 428 Minimum supply temperature trip-wire value where the supply will
>> 429 notify user-space of the event. This is normally used for the
>> 430 charging scenario where user-space needs to know the supply
>> 431 temperature has crossed a lower threshold so it can take
>> 432 appropriate action (e.g. warning user that the supply
>> 433 temperature is high, and charging current has been reduced
>> 434 accordingly to remedy the situation).
>> 435
>> 436 Access: Read
>> 437 Valid values: Represented in 1/10 Degrees Celsius
>> 438
>> 439 What: /sys/class/power_supply/<supply_name>/temp_max
>> 440 Date: July 2014
>> 441 Contact: linux-pm@vger.kernel.org
>> 442 Description:
>> 443 Reports the maximum allowed supply temperature for operation.
>> 444
>> 445 Access: Read
>> 446 Valid values: Represented in 1/10 Degrees Celsius
>> 447
>> 448 What: /sys/class/power_supply/<supply_name>/temp_min
>> 449 Date: July 2014
>> 450 Contact: linux-pm@vger.kernel.org
>> 451 Description:
>> 452 Reports the mainimum allowed supply temperature for operation.
>> 453
>> 454 Access: Read
>> 455 Valid values: Represented in 1/10 Degrees Celsius
602 456
603 What: /sys/class/power_supply/<suppl 457 What: /sys/class/power_supply/<supply_name>/usb_type
604 Date: March 2018 458 Date: March 2018
605 Contact: linux-pm@vger.kernel.org 459 Contact: linux-pm@vger.kernel.org
606 Description: 460 Description:
607 Reports what type of USB conne 461 Reports what type of USB connection is currently active for
608 the supply, for example it can 462 the supply, for example it can show if USB-PD capable source
609 is attached. 463 is attached.
610 464
611 Access: For power-supplies whi !! 465 Access: Read-Only
612 as battery charger chips, this !! 466 Valid values: "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
613 the connected USB power source !! 467 "PD_DRP", "PD_PPS", "BrickID"
614 468
615 For power-supplies which act a !! 469 What: /sys/class/power_supply/<supply_name>/voltage_max
616 e.g. the UCS1002 USB Port Powe !! 470 Date: January 2008
>> 471 Contact: linux-pm@vger.kernel.org
>> 472 Description:
>> 473 Reports the maximum VBUS voltage the supply can support.
617 474
618 Valid values: !! 475 Access: Read
619 "Unknown", "SDP" !! 476 Valid values: Represented in microvolts
620 "PD_DRP", "PD_PP <<
621 477
622 **Device Specific Properties** !! 478 What: /sys/class/power_supply/<supply_name>/voltage_min
>> 479 Date: January 2008
>> 480 Contact: linux-pm@vger.kernel.org
>> 481 Description:
>> 482 Reports the minimum VBUS voltage the supply can support.
>> 483
>> 484 Access: Read
>> 485 Valid values: Represented in microvolts
>> 486
>> 487 What: /sys/class/power_supply/<supply_name>/voltage_now
>> 488 Date: May 2007
>> 489 Contact: linux-pm@vger.kernel.org
>> 490 Description:
>> 491 Reports the VBUS voltage supplied now. This value is generally
>> 492 read-only reporting, unless the 'online' state of the supply
>> 493 is set to be programmable, in which case this value can be set
>> 494 within the reported min/max range.
>> 495
>> 496 Access: Read, Write
>> 497 Valid values: Represented in microvolts
>> 498
>> 499 ===== Device Specific Properties =====
623 500
624 What: /sys/class/power/ds2760-batter 501 What: /sys/class/power/ds2760-battery.*/charge_now
625 Date: May 2010 502 Date: May 2010
626 KernelVersion: 2.6.35 503 KernelVersion: 2.6.35
627 Contact: Daniel Mack <daniel@caiaq.de> 504 Contact: Daniel Mack <daniel@caiaq.de>
628 Description: 505 Description:
629 This file is writeable and can 506 This file is writeable and can be used to set the current
630 coloumb counter value inside t 507 coloumb counter value inside the battery monitor chip. This
631 is needed for unavoidable corr 508 is needed for unavoidable corrections of aging batteries.
632 A userspace daemon can monitor 509 A userspace daemon can monitor the battery charging logic
633 and once the counter drops out 510 and once the counter drops out of considerable bounds, take
634 appropriate action. 511 appropriate action.
635 512
636 What: /sys/class/power/ds2760-batter 513 What: /sys/class/power/ds2760-battery.*/charge_full
637 Date: May 2010 514 Date: May 2010
638 KernelVersion: 2.6.35 515 KernelVersion: 2.6.35
639 Contact: Daniel Mack <daniel@caiaq.de> 516 Contact: Daniel Mack <daniel@caiaq.de>
640 Description: 517 Description:
641 This file is writeable and can 518 This file is writeable and can be used to set the assumed
642 battery 'full level'. As batte 519 battery 'full level'. As batteries age, this value has to be
643 amended over time. 520 amended over time.
644 521
645 What: /sys/class/power_supply/max145 522 What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
646 Date: October 2014 523 Date: October 2014
647 KernelVersion: 3.18.0 524 KernelVersion: 3.18.0
648 Contact: Krzysztof Kozlowski <krzk@kerne 525 Contact: Krzysztof Kozlowski <krzk@kernel.org>
649 Description: 526 Description:
650 This entry shows and sets the 527 This entry shows and sets the maximum time the max14577
651 charger operates in fast-charg 528 charger operates in fast-charge mode. When the timer expires
652 the device will terminate fast 529 the device will terminate fast-charge mode (charging current
653 will drop to 0 A) and will tri 530 will drop to 0 A) and will trigger interrupt.
654 531
655 Valid values: 532 Valid values:
656 <<
657 - 5, 6 or 7 (hours), 533 - 5, 6 or 7 (hours),
658 - 0: disabled. 534 - 0: disabled.
659 535
660 What: /sys/class/power_supply/max776 536 What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer
661 Date: January 2015 537 Date: January 2015
662 KernelVersion: 3.19.0 538 KernelVersion: 3.19.0
663 Contact: Krzysztof Kozlowski <krzk@kerne 539 Contact: Krzysztof Kozlowski <krzk@kernel.org>
664 Description: 540 Description:
665 This entry shows and sets the 541 This entry shows and sets the maximum time the max77693
666 charger operates in fast-charg 542 charger operates in fast-charge mode. When the timer expires
667 the device will terminate fast 543 the device will terminate fast-charge mode (charging current
668 will drop to 0 A) and will tri 544 will drop to 0 A) and will trigger interrupt.
669 545
670 Valid values: 546 Valid values:
671 <<
672 - 4 - 16 (hours), step by 2 (r 547 - 4 - 16 (hours), step by 2 (rounded down)
673 - 0: disabled. 548 - 0: disabled.
674 549
675 What: /sys/class/power_supply/max776 550 What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
676 Date: January 2015 551 Date: January 2015
677 KernelVersion: 3.19.0 552 KernelVersion: 3.19.0
678 Contact: Krzysztof Kozlowski <krzk@kerne 553 Contact: Krzysztof Kozlowski <krzk@kernel.org>
679 Description: 554 Description:
680 This entry shows and sets the 555 This entry shows and sets the charging current threshold for
681 entering top-off charging mode 556 entering top-off charging mode. When charging current in fast
682 charge mode drops below this v 557 charge mode drops below this value, the charger will trigger
683 interrupt and start top-off ch 558 interrupt and start top-off charging mode.
684 559
685 Valid values: 560 Valid values:
686 <<
687 - 100000 - 200000 (microamps), 561 - 100000 - 200000 (microamps), step by 25000 (rounded down)
688 - 200000 - 350000 (microamps), 562 - 200000 - 350000 (microamps), step by 50000 (rounded down)
689 - 0: disabled. 563 - 0: disabled.
690 564
691 What: /sys/class/power_supply/max776 565 What: /sys/class/power_supply/max77693-charger/device/top_off_timer
692 Date: January 2015 566 Date: January 2015
693 KernelVersion: 3.19.0 567 KernelVersion: 3.19.0
694 Contact: Krzysztof Kozlowski <krzk@kerne 568 Contact: Krzysztof Kozlowski <krzk@kernel.org>
695 Description: 569 Description:
696 This entry shows and sets the 570 This entry shows and sets the maximum time the max77693
697 charger operates in top-off ch 571 charger operates in top-off charge mode. When the timer expires
698 the device will terminate top- 572 the device will terminate top-off charge mode (charging current
699 will drop to 0 A) and will tri 573 will drop to 0 A) and will trigger interrupt.
700 574
701 Valid values: 575 Valid values:
702 <<
703 - 0 - 70 (minutes), step by 10 576 - 0 - 70 (minutes), step by 10 (rounded down)
704 577
705 What: /sys/class/power_supply/bq2425 578 What: /sys/class/power_supply/bq24257-charger/ovp_voltage
706 Date: October 2015 579 Date: October 2015
707 KernelVersion: 4.4.0 580 KernelVersion: 4.4.0
708 Contact: Andreas Dannenberg <dannenberg@ 581 Contact: Andreas Dannenberg <dannenberg@ti.com>
709 Description: 582 Description:
710 This entry configures the over 583 This entry configures the overvoltage protection feature of bq24257-
711 type charger devices. This fea 584 type charger devices. This feature protects the device and other
712 components against damage from 585 components against damage from overvoltage on the input supply. See
713 device datasheet for details. 586 device datasheet for details.
714 587
715 Valid values: 588 Valid values:
716 <<
717 - 6000000, 6500000, 7000000, 8 589 - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
718 10500000 (all uV) 590 10500000 (all uV)
719 591
720 What: /sys/class/power_supply/bq2425 592 What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage
721 Date: October 2015 593 Date: October 2015
722 KernelVersion: 4.4.0 594 KernelVersion: 4.4.0
723 Contact: Andreas Dannenberg <dannenberg@ 595 Contact: Andreas Dannenberg <dannenberg@ti.com>
724 Description: 596 Description:
725 This entry configures the inpu 597 This entry configures the input dynamic power path management voltage of
726 bq24257-type charger devices. 598 bq24257-type charger devices. Once the supply drops to the configured
727 voltage, the input current lim 599 voltage, the input current limit is reduced down to prevent the further
728 drop of the supply. When the I 600 drop of the supply. When the IC enters this mode, the charge current is
729 lower than the set value. See 601 lower than the set value. See device datasheet for details.
730 602
731 Valid values: 603 Valid values:
732 <<
733 - 4200000, 4280000, 4360000, 4 604 - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
734 4760000 (all uV) 605 4760000 (all uV)
735 606
736 What: /sys/class/power_supply/bq2425 607 What: /sys/class/power_supply/bq24257-charger/high_impedance_enable
737 Date: October 2015 608 Date: October 2015
738 KernelVersion: 4.4.0 609 KernelVersion: 4.4.0
739 Contact: Andreas Dannenberg <dannenberg@ 610 Contact: Andreas Dannenberg <dannenberg@ti.com>
740 Description: 611 Description:
741 This entry allows enabling the 612 This entry allows enabling the high-impedance mode of bq24257-type
742 charger devices. If enabled, i 613 charger devices. If enabled, it places the charger IC into low power
743 standby mode with the switch m 614 standby mode with the switch mode controller disabled. When disabled,
744 the charger operates normally. 615 the charger operates normally. See device datasheet for details.
745 616
746 Valid values: 617 Valid values:
747 <<
748 - 1: enabled 618 - 1: enabled
749 - 0: disabled 619 - 0: disabled
750 620
751 What: /sys/class/power_supply/bq2425 621 What: /sys/class/power_supply/bq24257-charger/sysoff_enable
752 Date: October 2015 622 Date: October 2015
753 KernelVersion: 4.4.0 623 KernelVersion: 4.4.0
754 Contact: Andreas Dannenberg <dannenberg@ 624 Contact: Andreas Dannenberg <dannenberg@ti.com>
755 Description: 625 Description:
756 This entry allows enabling the 626 This entry allows enabling the sysoff mode of bq24257-type charger
757 devices. If enabled and the in 627 devices. If enabled and the input is removed, the internal battery FET
758 is turned off in order to redu 628 is turned off in order to reduce the leakage from the BAT pin to less
759 than 1uA. Note that on some de 629 than 1uA. Note that on some devices/systems this disconnects the battery
760 from the system. See device da 630 from the system. See device datasheet for details.
761 631
762 Valid values: 632 Valid values:
763 <<
764 - 1: enabled 633 - 1: enabled
765 - 0: disabled 634 - 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.