1 ===== General Properties =====
3 What: /sys/class/power_supply/<supply_name>/manufacturer
5 Contact: linux-pm@vger.kernel.org
7 Reports the name of the device manufacturer.
10 Valid values: Represented as string
12 What: /sys/class/power_supply/<supply_name>/model_name
14 Contact: linux-pm@vger.kernel.org
16 Reports the name of the device model.
19 Valid values: Represented as string
21 What: /sys/class/power_supply/<supply_name>/serial_number
23 Contact: linux-pm@vger.kernel.org
25 Reports the serial number of the device.
28 Valid values: Represented as string
30 What: /sys/class/power_supply/<supply_name>/type
32 Contact: linux-pm@vger.kernel.org
34 Describes the main type of the supply.
37 Valid values: "Battery", "UPS", "Mains", "USB"
39 ===== Battery Properties =====
41 What: /sys/class/power_supply/<supply_name>/capacity
43 Contact: linux-pm@vger.kernel.org
45 Fine grain representation of battery capacity.
47 Valid values: 0 - 100 (percent)
49 What: /sys/class/power_supply/<supply_name>/capacity_alert_max
51 Contact: linux-pm@vger.kernel.org
53 Maximum battery capacity trip-wire value where the supply will
54 notify user-space of the event. This is normally used for the
55 battery discharging scenario where user-space needs to know the
56 battery has dropped to an upper level so it can take
57 appropriate action (e.g. warning user that battery level is
61 Valid values: 0 - 100 (percent)
63 What: /sys/class/power_supply/<supply_name>/capacity_alert_min
65 Contact: linux-pm@vger.kernel.org
67 Minimum battery capacity trip-wire value where the supply will
68 notify user-space of the event. This is normally used for the
69 battery discharging scenario where user-space needs to know the
70 battery has dropped to a lower level so it can take
71 appropriate action (e.g. warning user that battery level is
75 Valid values: 0 - 100 (percent)
77 What: /sys/class/power_supply/<supply_name>/capacity_level
79 Contact: linux-pm@vger.kernel.org
81 Coarse representation of battery capacity.
84 Valid values: "Unknown", "Critical", "Low", "Normal", "High",
87 What: /sys/class/power_supply/<supply_name>/current_avg
89 Contact: linux-pm@vger.kernel.org
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.
96 Valid values: Represented in microamps
98 What: /sys/class/power_supply/<supply_name>/current_max
100 Contact: linux-pm@vger.kernel.org
102 Reports the maximum IBAT current allowed into the battery.
105 Valid values: Represented in microamps
107 What: /sys/class/power_supply/<supply_name>/current_now
109 Contact: linux-pm@vger.kernel.org
111 Reports an instant, single IBAT current reading for the battery.
112 This value is not averaged/smoothed.
115 Valid values: Represented in microamps
117 What: /sys/class/power_supply/<supply_name>/charge_control_limit
119 Contact: linux-pm@vger.kernel.org
121 Maximum allowable charging current. Used for charge rate
122 throttling for thermal cooling or improving battery health.
125 Valid values: Represented in microamps
127 What: /sys/class/power_supply/<supply_name>/charge_control_limit_max
129 Contact: linux-pm@vger.kernel.org
131 Maximum legal value for the charge_control_limit property.
134 Valid values: Represented in microamps
136 What: /sys/class/power_supply/<supply_name>/charge_control_start_threshold
138 Contact: linux-pm@vger.kernel.org
140 Represents a battery percentage level, below which charging will
144 Valid values: 0 - 100 (percent)
146 What: /sys/class/power_supply/<supply_name>/charge_control_end_threshold
148 Contact: linux-pm@vger.kernel.org
150 Represents a battery percentage level, above which charging will
154 Valid values: 0 - 100 (percent)
156 What: /sys/class/power_supply/<supply_name>/charge_type
158 Contact: linux-pm@vger.kernel.org
160 Represents the type of charging currently being applied to the
161 battery. "Trickle", "Fast", and "Standard" all mean different
162 charging speeds. "Adaptive" means that the charger uses some
163 algorithm to adjust the charge rate dynamically, without
164 any user configuration required. "Custom" means that the charger
165 uses the charge_control_* properties as configuration for some
169 Valid values: "Unknown", "N/A", "Trickle", "Fast", "Standard",
172 What: /sys/class/power_supply/<supply_name>/charge_term_current
174 Contact: linux-pm@vger.kernel.org
176 Reports the charging current value which is used to determine
177 when the battery is considered full and charging should end.
180 Valid values: Represented in microamps
182 What: /sys/class/power_supply/<supply_name>/health
184 Contact: linux-pm@vger.kernel.org
186 Reports the health of the battery or battery side of charger
190 Valid values: "Unknown", "Good", "Overheat", "Dead",
191 "Over voltage", "Unspecified failure", "Cold",
192 "Watchdog timer expire", "Safety timer expire"
194 What: /sys/class/power_supply/<supply_name>/precharge_current
196 Contact: linux-pm@vger.kernel.org
198 Reports the charging current applied during pre-charging phase
199 for a battery charge cycle.
202 Valid values: Represented in microamps
204 What: /sys/class/power_supply/<supply_name>/present
206 Contact: linux-pm@vger.kernel.org
208 Reports whether a battery is present or not in the system.
215 What: /sys/class/power_supply/<supply_name>/status
217 Contact: linux-pm@vger.kernel.org
219 Represents the charging status of the battery. Normally this
220 is read-only reporting although for some supplies this can be
221 used to enable/disable charging to the battery.
224 Valid values: "Unknown", "Charging", "Discharging",
225 "Not charging", "Full"
227 What: /sys/class/power_supply/<supply_name>/technology
229 Contact: linux-pm@vger.kernel.org
231 Describes the battery technology supported by the supply.
234 Valid values: "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
237 What: /sys/class/power_supply/<supply_name>/temp
239 Contact: linux-pm@vger.kernel.org
241 Reports the current TBAT battery temperature reading.
244 Valid values: Represented in 1/10 Degrees Celsius
246 What: /sys/class/power_supply/<supply_name>/temp_alert_max
248 Contact: linux-pm@vger.kernel.org
250 Maximum TBAT temperature trip-wire value where the supply will
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).
258 Valid values: Represented in 1/10 Degrees Celsius
260 What: /sys/class/power_supply/<supply_name>/temp_alert_min
262 Contact: linux-pm@vger.kernel.org
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).
273 Valid values: Represented in 1/10 Degrees Celsius
275 What: /sys/class/power_supply/<supply_name>/temp_max
277 Contact: linux-pm@vger.kernel.org
279 Reports the maximum allowed TBAT battery temperature for
283 Valid values: Represented in 1/10 Degrees Celsius
285 What: /sys/class/power_supply/<supply_name>/temp_min
287 Contact: linux-pm@vger.kernel.org
289 Reports the minimum allowed TBAT battery temperature for
293 Valid values: Represented in 1/10 Degrees Celsius
295 What: /sys/class/power_supply/<supply_name>/voltage_avg,
297 Contact: linux-pm@vger.kernel.org
299 Reports an average VBAT voltage reading for the battery, over a
300 fixed period. Normally devices will provide a fixed interval in
301 which they average readings to smooth out the reported value.
304 Valid values: Represented in microvolts
306 What: /sys/class/power_supply/<supply_name>/voltage_max,
308 Contact: linux-pm@vger.kernel.org
310 Reports the maximum safe VBAT voltage permitted for the battery,
314 Valid values: Represented in microvolts
316 What: /sys/class/power_supply/<supply_name>/voltage_min,
318 Contact: linux-pm@vger.kernel.org
320 Reports the minimum safe VBAT voltage permitted for the battery,
324 Valid values: Represented in microvolts
326 What: /sys/class/power_supply/<supply_name>/voltage_now,
328 Contact: linux-pm@vger.kernel.org
330 Reports an instant, single VBAT voltage reading for the battery.
331 This value is not averaged/smoothed.
334 Valid values: Represented in microvolts
336 ===== USB Properties =====
338 What: /sys/class/power_supply/<supply_name>/current_avg
340 Contact: linux-pm@vger.kernel.org
342 Reports an average IBUS current reading over a fixed period.
343 Normally devices will provide a fixed interval in which they
344 average readings to smooth out the reported value.
347 Valid values: Represented in microamps
350 What: /sys/class/power_supply/<supply_name>/current_max
352 Contact: linux-pm@vger.kernel.org
354 Reports the maximum IBUS current the supply can support.
357 Valid values: Represented in microamps
359 What: /sys/class/power_supply/<supply_name>/current_now
361 Contact: linux-pm@vger.kernel.org
363 Reports the IBUS current supplied now. This value is generally
364 read-only reporting, unless the 'online' state of the supply
365 is set to be programmable, in which case this value can be set
366 within the reported min/max range.
369 Valid values: Represented in microamps
371 What: /sys/class/power_supply/<supply_name>/input_current_limit
373 Contact: linux-pm@vger.kernel.org
375 Details the incoming IBUS current limit currently set in the
376 supply. Normally this is configured based on the type of
377 connection made (e.g. A configured SDP should output a maximum
378 of 500mA so the input current limit is set to the same value).
381 Valid values: Represented in microamps
383 What: /sys/class/power_supply/<supply_name>/online,
385 Contact: linux-pm@vger.kernel.org
387 Indicates if VBUS is present for the supply. When the supply is
388 online, and the supply allows it, then it's possible to switch
389 between online states (e.g. Fixed -> Programmable for a PD_PPS
390 USB supply so voltage and current can be controlled).
395 1: Online Fixed - Fixed Voltage Supply
396 2: Online Programmable - Programmable Voltage Supply
398 What: /sys/class/power_supply/<supply_name>/temp
400 Contact: linux-pm@vger.kernel.org
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)
407 Valid values: Represented in 1/10 Degrees Celsius
409 What: /sys/class/power_supply/<supply_name>/temp_alert_max
411 Contact: linux-pm@vger.kernel.org
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).
422 Valid values: Represented in 1/10 Degrees Celsius
424 What: /sys/class/power_supply/<supply_name>/temp_alert_min
426 Contact: linux-pm@vger.kernel.org
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).
437 Valid values: Represented in 1/10 Degrees Celsius
439 What: /sys/class/power_supply/<supply_name>/temp_max
441 Contact: linux-pm@vger.kernel.org
443 Reports the maximum allowed supply temperature for operation.
446 Valid values: Represented in 1/10 Degrees Celsius
448 What: /sys/class/power_supply/<supply_name>/temp_min
450 Contact: linux-pm@vger.kernel.org
452 Reports the mainimum allowed supply temperature for operation.
455 Valid values: Represented in 1/10 Degrees Celsius
457 What: /sys/class/power_supply/<supply_name>/usb_type
459 Contact: linux-pm@vger.kernel.org
461 Reports what type of USB connection is currently active for
462 the supply, for example it can show if USB-PD capable source
466 Valid values: "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
467 "PD_DRP", "PD_PPS", "BrickID"
469 What: /sys/class/power_supply/<supply_name>/voltage_max
471 Contact: linux-pm@vger.kernel.org
473 Reports the maximum VBUS voltage the supply can support.
476 Valid values: Represented in microvolts
478 What: /sys/class/power_supply/<supply_name>/voltage_min
480 Contact: linux-pm@vger.kernel.org
482 Reports the minimum VBUS voltage the supply can support.
485 Valid values: Represented in microvolts
487 What: /sys/class/power_supply/<supply_name>/voltage_now
489 Contact: linux-pm@vger.kernel.org
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.
497 Valid values: Represented in microvolts
499 ===== Device Specific Properties =====
501 What: /sys/class/power/ds2760-battery.*/charge_now
503 KernelVersion: 2.6.35
504 Contact: Daniel Mack <daniel@caiaq.de>
506 This file is writeable and can be used to set the current
507 coloumb counter value inside the battery monitor chip. This
508 is needed for unavoidable corrections of aging batteries.
509 A userspace daemon can monitor the battery charging logic
510 and once the counter drops out of considerable bounds, take
513 What: /sys/class/power/ds2760-battery.*/charge_full
515 KernelVersion: 2.6.35
516 Contact: Daniel Mack <daniel@caiaq.de>
518 This file is writeable and can be used to set the assumed
519 battery 'full level'. As batteries age, this value has to be
522 What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
524 KernelVersion: 3.18.0
525 Contact: Krzysztof Kozlowski <krzk@kernel.org>
527 This entry shows and sets the maximum time the max14577
528 charger operates in fast-charge mode. When the timer expires
529 the device will terminate fast-charge mode (charging current
530 will drop to 0 A) and will trigger interrupt.
536 What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer
538 KernelVersion: 3.19.0
539 Contact: Krzysztof Kozlowski <krzk@kernel.org>
541 This entry shows and sets the maximum time the max77693
542 charger operates in fast-charge mode. When the timer expires
543 the device will terminate fast-charge mode (charging current
544 will drop to 0 A) and will trigger interrupt.
547 - 4 - 16 (hours), step by 2 (rounded down)
550 What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
552 KernelVersion: 3.19.0
553 Contact: Krzysztof Kozlowski <krzk@kernel.org>
555 This entry shows and sets the charging current threshold for
556 entering top-off charging mode. When charging current in fast
557 charge mode drops below this value, the charger will trigger
558 interrupt and start top-off charging mode.
561 - 100000 - 200000 (microamps), step by 25000 (rounded down)
562 - 200000 - 350000 (microamps), step by 50000 (rounded down)
565 What: /sys/class/power_supply/max77693-charger/device/top_off_timer
567 KernelVersion: 3.19.0
568 Contact: Krzysztof Kozlowski <krzk@kernel.org>
570 This entry shows and sets the maximum time the max77693
571 charger operates in top-off charge mode. When the timer expires
572 the device will terminate top-off charge mode (charging current
573 will drop to 0 A) and will trigger interrupt.
576 - 0 - 70 (minutes), step by 10 (rounded down)
578 What: /sys/class/power_supply/bq24257-charger/ovp_voltage
581 Contact: Andreas Dannenberg <dannenberg@ti.com>
583 This entry configures the overvoltage protection feature of bq24257-
584 type charger devices. This feature protects the device and other
585 components against damage from overvoltage on the input supply. See
586 device datasheet for details.
589 - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
592 What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage
595 Contact: Andreas Dannenberg <dannenberg@ti.com>
597 This entry configures the input dynamic power path management voltage of
598 bq24257-type charger devices. Once the supply drops to the configured
599 voltage, the input current limit is reduced down to prevent the further
600 drop of the supply. When the IC enters this mode, the charge current is
601 lower than the set value. See device datasheet for details.
604 - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
607 What: /sys/class/power_supply/bq24257-charger/high_impedance_enable
610 Contact: Andreas Dannenberg <dannenberg@ti.com>
612 This entry allows enabling the high-impedance mode of bq24257-type
613 charger devices. If enabled, it places the charger IC into low power
614 standby mode with the switch mode controller disabled. When disabled,
615 the charger operates normally. See device datasheet for details.
621 What: /sys/class/power_supply/bq24257-charger/sysoff_enable
624 Contact: Andreas Dannenberg <dannenberg@ti.com>
626 This entry allows enabling the sysoff mode of bq24257-type charger
627 devices. If enabled and the input is removed, the internal battery FET
628 is turned off in order to reduce the leakage from the BAT pin to less
629 than 1uA. Note that on some devices/systems this disconnects the battery
630 from the system. See device datasheet for details.