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