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