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", "Wireless"
39 **Battery and USB properties**
41 What: /sys/class/power_supply/<supply_name>/current_avg
43 Contact: linux-pm@vger.kernel.org
47 Reports an average IBAT current reading for the battery, over
48 a fixed period. Normally devices will provide a fixed interval
49 in which they average readings to smooth out the reported
54 Reports an average IBUS current reading over a fixed period.
55 Normally devices will provide a fixed interval in which they
56 average readings to smooth out the reported value.
60 Valid values: Represented in microamps. Negative values are
61 used for discharging batteries, positive values for charging
62 batteries and for USB IBUS current.
64 What: /sys/class/power_supply/<supply_name>/current_max
66 Contact: linux-pm@vger.kernel.org
70 Reports the maximum IBAT current allowed into the battery.
74 Reports the maximum IBUS current the supply can support.
77 Valid values: Represented in microamps
79 What: /sys/class/power_supply/<supply_name>/current_now
81 Contact: linux-pm@vger.kernel.org
86 Reports an instant, single IBAT current reading for the
87 battery. This value is not averaged/smoothed.
93 Reports the IBUS current supplied now. This value is generally
94 read-only reporting, unless the 'online' state of the supply
95 is set to be programmable, in which case this value can be set
96 within the reported min/max range.
100 Valid values: Represented in microamps. Negative values are
101 used for discharging batteries, positive values for charging
102 batteries and for USB IBUS current.
104 What: /sys/class/power_supply/<supply_name>/temp
106 Contact: linux-pm@vger.kernel.org
110 Reports the current TBAT battery temperature reading.
114 Reports the current supply temperature reading. This would
115 normally be the internal temperature of the device itself
116 (e.g TJUNC temperature of an IC)
120 Valid values: Represented in 1/10 Degrees Celsius
122 What: /sys/class/power_supply/<supply_name>/temp_alert_max
124 Contact: linux-pm@vger.kernel.org
128 Maximum TBAT temperature trip-wire value where the supply will
129 notify user-space of the event.
133 Maximum supply temperature trip-wire value where the supply
134 will notify user-space of the event.
136 This is normally used for the charging scenario where
137 user-space needs to know if the temperature has crossed an
138 upper threshold so it can take appropriate action (e.g. warning
139 user that the temperature is critically high, and charging has
144 Valid values: Represented in 1/10 Degrees Celsius
146 What: /sys/class/power_supply/<supply_name>/temp_alert_min
148 Contact: linux-pm@vger.kernel.org
153 Minimum TBAT temperature trip-wire value where the supply will
154 notify user-space of the event.
158 Minimum supply temperature trip-wire value where the supply
159 will notify user-space of the event.
161 This is normally used for the charging scenario where user-space
162 needs to know if the temperature has crossed a lower threshold
163 so it can take appropriate action (e.g. warning user that
164 temperature level is high, and charging current has been
165 reduced accordingly to remedy the situation).
169 Valid values: Represented in 1/10 Degrees Celsius
171 What: /sys/class/power_supply/<supply_name>/temp_max
173 Contact: linux-pm@vger.kernel.org
177 Reports the maximum allowed TBAT battery temperature for
182 Reports the maximum allowed supply temperature for operation.
186 Valid values: Represented in 1/10 Degrees Celsius
188 What: /sys/class/power_supply/<supply_name>/temp_min
190 Contact: linux-pm@vger.kernel.org
194 Reports the minimum allowed TBAT battery temperature for
199 Reports the minimum allowed supply temperature for operation.
203 Valid values: Represented in 1/10 Degrees Celsius
205 What: /sys/class/power_supply/<supply_name>/voltage_max,
207 Contact: linux-pm@vger.kernel.org
211 Reports the maximum safe VBAT voltage permitted for the
212 battery, during charging.
216 Reports the maximum VBUS voltage the supply can support.
220 Valid values: Represented in microvolts
222 What: /sys/class/power_supply/<supply_name>/voltage_min,
224 Contact: linux-pm@vger.kernel.org
228 Reports the minimum safe VBAT voltage permitted for the
229 battery, during discharging.
233 Reports the minimum VBUS voltage the supply can support.
237 Valid values: Represented in microvolts
239 What: /sys/class/power_supply/<supply_name>/voltage_now,
241 Contact: linux-pm@vger.kernel.org
245 Reports an instant, single VBAT voltage reading for the
246 battery. This value is not averaged/smoothed.
252 Reports the VBUS voltage supplied now. This value is generally
253 read-only reporting, unless the 'online' state of the supply
254 is set to be programmable, in which case this value can be set
255 within the reported min/max range.
259 Valid values: Represented in microvolts
261 **Battery Properties**
263 What: /sys/class/power_supply/<supply_name>/capacity
265 Contact: linux-pm@vger.kernel.org
267 Fine grain representation of battery capacity.
271 Valid values: 0 - 100 (percent)
273 What: /sys/class/power_supply/<supply_name>/capacity_alert_max
275 Contact: linux-pm@vger.kernel.org
277 Maximum battery capacity trip-wire value where the supply will
278 notify user-space of the event. This is normally used for the
279 battery discharging scenario where user-space needs to know the
280 battery has dropped to an upper level so it can take
281 appropriate action (e.g. warning user that battery level is
286 Valid values: 0 - 100 (percent)
288 What: /sys/class/power_supply/<supply_name>/capacity_alert_min
290 Contact: linux-pm@vger.kernel.org
292 Minimum battery capacity trip-wire value where the supply will
293 notify user-space of the event. This is normally used for the
294 battery discharging scenario where user-space needs to know the
295 battery has dropped to a lower level so it can take
296 appropriate action (e.g. warning user that battery level is
301 Valid values: 0 - 100 (percent)
303 What: /sys/class/power_supply/<supply_name>/capacity_error_margin
305 Contact: linux-pm@vger.kernel.org
307 Battery capacity measurement becomes unreliable without
308 recalibration. This values provides the maximum error
309 margin expected to exist by the fuel gauge in percent.
310 Values close to 0% will be returned after (re-)calibration
311 has happened. Over time the error margin will increase.
312 100% means, that the capacity related values are basically
317 Valid values: 0 - 100 (percent)
319 What: /sys/class/power_supply/<supply_name>/capacity_level
321 Contact: linux-pm@vger.kernel.org
323 Coarse representation of battery capacity.
328 "Unknown", "Critical", "Low", "Normal", "High",
331 What: /sys/class/power_supply/<supply_name>/charge_control_limit
333 Contact: linux-pm@vger.kernel.org
335 Maximum allowable charging current. Used for charge rate
336 throttling for thermal cooling or improving battery health.
340 Valid values: Represented in microamps
342 What: /sys/class/power_supply/<supply_name>/charge_control_limit_max
344 Contact: linux-pm@vger.kernel.org
346 Maximum legal value for the charge_control_limit property.
350 Valid values: Represented in microamps
352 What: /sys/class/power_supply/<supply_name>/charge_control_start_threshold
354 Contact: linux-pm@vger.kernel.org
356 Represents a battery percentage level, below which charging will
360 Valid values: 0 - 100 (percent)
362 What: /sys/class/power_supply/<supply_name>/charge_control_end_threshold
364 Contact: linux-pm@vger.kernel.org
366 Represents a battery percentage level, above which charging will
371 Valid values: 0 - 100 (percent)
373 What: /sys/class/power_supply/<supply_name>/charge_type
375 Contact: linux-pm@vger.kernel.org
377 Represents the type of charging currently being applied to the
378 battery. "Trickle", "Fast", and "Standard" all mean different
379 charging speeds. "Adaptive" means that the charger uses some
380 algorithm to adjust the charge rate dynamically, without
381 any user configuration required. "Custom" means that the charger
382 uses the charge_control_* properties as configuration for some
383 different algorithm. "Long Life" means the charger reduces its
384 charging rate in order to prolong the battery health. "Bypass"
385 means the charger bypasses the charging path around the
386 integrated converter allowing for a "smart" wall adaptor to
387 perform the power conversion externally.
392 "Unknown", "N/A", "Trickle", "Fast", "Standard",
393 "Adaptive", "Custom", "Long Life", "Bypass"
395 What: /sys/class/power_supply/<supply_name>/charge_term_current
397 Contact: linux-pm@vger.kernel.org
399 Reports the charging current value which is used to determine
400 when the battery is considered full and charging should end.
404 Valid values: Represented in microamps
406 What: /sys/class/power_supply/<supply_name>/health
408 Contact: linux-pm@vger.kernel.org
410 Reports the health of the battery or battery side of charger
416 "Unknown", "Good", "Overheat", "Dead",
417 "Over voltage", "Unspecified failure", "Cold",
418 "Watchdog timer expire", "Safety timer expire",
419 "Over current", "Calibration required", "Warm",
420 "Cool", "Hot", "No battery"
422 What: /sys/class/power_supply/<supply_name>/precharge_current
424 Contact: linux-pm@vger.kernel.org
426 Reports the charging current applied during pre-charging phase
427 for a battery charge cycle.
431 Valid values: Represented in microamps
433 What: /sys/class/power_supply/<supply_name>/present
435 Contact: linux-pm@vger.kernel.org
437 Reports whether a battery is present or not in the system.
448 What: /sys/class/power_supply/<supply_name>/status
450 Contact: linux-pm@vger.kernel.org
452 Represents the charging status of the battery. Normally this
453 is read-only reporting although for some supplies this can be
454 used to enable/disable charging to the battery.
459 "Unknown", "Charging", "Discharging",
460 "Not charging", "Full"
462 What: /sys/class/power_supply/<supply_name>/charge_behaviour
464 Contact: linux-pm@vger.kernel.org
466 Represents the charging behaviour.
471 ================ ====================================
472 auto: Charge normally, respect thresholds
473 inhibit-charge: Do not charge while AC is attached
474 force-discharge: Force discharge while AC is attached
475 ================ ====================================
477 What: /sys/class/power_supply/<supply_name>/technology
479 Contact: linux-pm@vger.kernel.org
481 Describes the battery technology supported by the supply.
486 "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
490 What: /sys/class/power_supply/<supply_name>/voltage_avg,
492 Contact: linux-pm@vger.kernel.org
494 Reports an average VBAT voltage reading for the battery, over a
495 fixed period. Normally devices will provide a fixed interval in
496 which they average readings to smooth out the reported value.
500 Valid values: Represented in microvolts
502 What: /sys/class/power_supply/<supply_name>/cycle_count
504 Contact: linux-pm@vger.kernel.org
506 Reports the number of full charge + discharge cycles the
507 battery has undergone.
512 Integer > 0: representing full cycles
513 Integer = 0: cycle_count info is not available
517 What: /sys/class/power_supply/<supply_name>/input_current_limit
519 Contact: linux-pm@vger.kernel.org
521 Details the incoming IBUS current limit currently set in the
522 supply. Normally this is configured based on the type of
523 connection made (e.g. A configured SDP should output a maximum
524 of 500mA so the input current limit is set to the same value).
525 Use preferably input_power_limit, and for problems that can be
526 solved using power limit use input_current_limit.
530 Valid values: Represented in microamps
532 What: /sys/class/power_supply/<supply_name>/input_voltage_limit
534 Contact: linux-pm@vger.kernel.org
536 This entry configures the incoming VBUS voltage limit currently
537 set in the supply. Normally this is configured based on
538 system-level knowledge or user input (e.g. This is part of the
539 Pixel C's thermal management strategy to effectively limit the
540 input power to 5V when the screen is on to meet Google's skin
541 temperature targets). Note that this feature should not be
542 used for safety critical things.
543 Use preferably input_power_limit, and for problems that can be
544 solved using power limit use input_voltage_limit.
548 Valid values: Represented in microvolts
550 What: /sys/class/power_supply/<supply_name>/input_power_limit
552 Contact: linux-pm@vger.kernel.org
554 This entry configures the incoming power limit currently set
555 in the supply. Normally this is configured based on
556 system-level knowledge or user input. Use preferably this
557 feature to limit the incoming power and use current/voltage
558 limit only for problems that can be solved using power limit.
562 Valid values: Represented in microwatts
564 What: /sys/class/power_supply/<supply_name>/online,
566 Contact: linux-pm@vger.kernel.org
568 Indicates if VBUS is present for the supply. When the supply is
569 online, and the supply allows it, then it's possible to switch
570 between online states (e.g. Fixed -> Programmable for a PD_PPS
571 USB supply so voltage and current can be controlled).
577 == ==================================================
579 1: Online Fixed - Fixed Voltage Supply
580 2: Online Programmable - Programmable Voltage Supply
581 == ==================================================
583 What: /sys/class/power_supply/<supply_name>/usb_type
585 Contact: linux-pm@vger.kernel.org
587 Reports what type of USB connection is currently active for
588 the supply, for example it can show if USB-PD capable source
594 "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
595 "PD_DRP", "PD_PPS", "BrickID"
597 **Device Specific Properties**
599 What: /sys/class/power/ds2760-battery.*/charge_now
601 KernelVersion: 2.6.35
602 Contact: Daniel Mack <daniel@caiaq.de>
604 This file is writeable and can be used to set the current
605 coloumb counter value inside the battery monitor chip. This
606 is needed for unavoidable corrections of aging batteries.
607 A userspace daemon can monitor the battery charging logic
608 and once the counter drops out of considerable bounds, take
611 What: /sys/class/power/ds2760-battery.*/charge_full
613 KernelVersion: 2.6.35
614 Contact: Daniel Mack <daniel@caiaq.de>
616 This file is writeable and can be used to set the assumed
617 battery 'full level'. As batteries age, this value has to be
620 What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
622 KernelVersion: 3.18.0
623 Contact: Krzysztof Kozlowski <krzk@kernel.org>
625 This entry shows and sets the maximum time the max14577
626 charger operates in fast-charge mode. When the timer expires
627 the device will terminate fast-charge mode (charging current
628 will drop to 0 A) and will trigger interrupt.
635 What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer
637 KernelVersion: 3.19.0
638 Contact: Krzysztof Kozlowski <krzk@kernel.org>
640 This entry shows and sets the maximum time the max77693
641 charger operates in fast-charge mode. When the timer expires
642 the device will terminate fast-charge mode (charging current
643 will drop to 0 A) and will trigger interrupt.
647 - 4 - 16 (hours), step by 2 (rounded down)
650 What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
652 KernelVersion: 3.19.0
653 Contact: Krzysztof Kozlowski <krzk@kernel.org>
655 This entry shows and sets the charging current threshold for
656 entering top-off charging mode. When charging current in fast
657 charge mode drops below this value, the charger will trigger
658 interrupt and start top-off charging mode.
662 - 100000 - 200000 (microamps), step by 25000 (rounded down)
663 - 200000 - 350000 (microamps), step by 50000 (rounded down)
666 What: /sys/class/power_supply/max77693-charger/device/top_off_timer
668 KernelVersion: 3.19.0
669 Contact: Krzysztof Kozlowski <krzk@kernel.org>
671 This entry shows and sets the maximum time the max77693
672 charger operates in top-off charge mode. When the timer expires
673 the device will terminate top-off charge mode (charging current
674 will drop to 0 A) and will trigger interrupt.
678 - 0 - 70 (minutes), step by 10 (rounded down)
680 What: /sys/class/power_supply/bq24257-charger/ovp_voltage
683 Contact: Andreas Dannenberg <dannenberg@ti.com>
685 This entry configures the overvoltage protection feature of bq24257-
686 type charger devices. This feature protects the device and other
687 components against damage from overvoltage on the input supply. See
688 device datasheet for details.
692 - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
695 What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage
698 Contact: Andreas Dannenberg <dannenberg@ti.com>
700 This entry configures the input dynamic power path management voltage of
701 bq24257-type charger devices. Once the supply drops to the configured
702 voltage, the input current limit is reduced down to prevent the further
703 drop of the supply. When the IC enters this mode, the charge current is
704 lower than the set value. See device datasheet for details.
708 - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
711 What: /sys/class/power_supply/bq24257-charger/high_impedance_enable
714 Contact: Andreas Dannenberg <dannenberg@ti.com>
716 This entry allows enabling the high-impedance mode of bq24257-type
717 charger devices. If enabled, it places the charger IC into low power
718 standby mode with the switch mode controller disabled. When disabled,
719 the charger operates normally. See device datasheet for details.
726 What: /sys/class/power_supply/bq24257-charger/sysoff_enable
729 Contact: Andreas Dannenberg <dannenberg@ti.com>
731 This entry allows enabling the sysoff mode of bq24257-type charger
732 devices. If enabled and the input is removed, the internal battery FET
733 is turned off in order to reduce the leakage from the BAT pin to less
734 than 1uA. Note that on some devices/systems this disconnects the battery
735 from the system. See device datasheet for details.
742 What: /sys/class/power_supply/<supply_name>/manufacture_year
744 Contact: linux-pm@vger.kernel.org
746 Reports the year (following Gregorian calendar) when the device has been
751 Valid values: Reported as integer
753 What: /sys/class/power_supply/<supply_name>/manufacture_month
755 Contact: linux-pm@vger.kernel.org
757 Reports the month when the device has been manufactured.
763 What: /sys/class/power_supply/<supply_name>/manufacture_day
765 Contact: linux-pm@vger.kernel.org
767 Reports the day of month when the device has been manufactured.