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
367 stop. Not all hardware is capable of setting this to an arbitrary
368 percentage. Drivers will round written values to the nearest
369 supported value. Reading back the value will show the actual
370 threshold set by the driver.
374 Valid values: 0 - 100 (percent)
376 What: /sys/class/power_supply/<supply_name>/charge_type
378 Contact: linux-pm@vger.kernel.org
380 Represents the type of charging currently being applied to the
381 battery. "Trickle", "Fast", and "Standard" all mean different
382 charging speeds. "Adaptive" means that the charger uses some
383 algorithm to adjust the charge rate dynamically, without
384 any user configuration required. "Custom" means that the charger
385 uses the charge_control_* properties as configuration for some
386 different algorithm. "Long Life" means the charger reduces its
387 charging rate in order to prolong the battery health. "Bypass"
388 means the charger bypasses the charging path around the
389 integrated converter allowing for a "smart" wall adaptor to
390 perform the power conversion externally.
395 "Unknown", "N/A", "Trickle", "Fast", "Standard",
396 "Adaptive", "Custom", "Long Life", "Bypass"
398 What: /sys/class/power_supply/<supply_name>/charge_term_current
400 Contact: linux-pm@vger.kernel.org
402 Reports the charging current value which is used to determine
403 when the battery is considered full and charging should end.
407 Valid values: Represented in microamps
409 What: /sys/class/power_supply/<supply_name>/health
411 Contact: linux-pm@vger.kernel.org
413 Reports the health of the battery or battery side of charger
419 "Unknown", "Good", "Overheat", "Dead",
420 "Over voltage", "Unspecified failure", "Cold",
421 "Watchdog timer expire", "Safety timer expire",
422 "Over current", "Calibration required", "Warm",
423 "Cool", "Hot", "No battery"
425 What: /sys/class/power_supply/<supply_name>/precharge_current
427 Contact: linux-pm@vger.kernel.org
429 Reports the charging current applied during pre-charging phase
430 for a battery charge cycle.
434 Valid values: Represented in microamps
436 What: /sys/class/power_supply/<supply_name>/present
438 Contact: linux-pm@vger.kernel.org
440 Reports whether a battery is present or not in the system.
451 What: /sys/class/power_supply/<supply_name>/status
453 Contact: linux-pm@vger.kernel.org
455 Represents the charging status of the battery. Normally this
456 is read-only reporting although for some supplies this can be
457 used to enable/disable charging to the battery.
462 "Unknown", "Charging", "Discharging",
463 "Not charging", "Full"
465 What: /sys/class/power_supply/<supply_name>/charge_behaviour
467 Contact: linux-pm@vger.kernel.org
469 Represents the charging behaviour.
474 ================ ====================================
475 auto: Charge normally, respect thresholds
476 inhibit-charge: Do not charge while AC is attached
477 force-discharge: Force discharge while AC is attached
478 ================ ====================================
480 What: /sys/class/power_supply/<supply_name>/technology
482 Contact: linux-pm@vger.kernel.org
484 Describes the battery technology supported by the supply.
489 "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
493 What: /sys/class/power_supply/<supply_name>/voltage_avg,
495 Contact: linux-pm@vger.kernel.org
497 Reports an average VBAT voltage reading for the battery, over a
498 fixed period. Normally devices will provide a fixed interval in
499 which they average readings to smooth out the reported value.
503 Valid values: Represented in microvolts
505 What: /sys/class/power_supply/<supply_name>/cycle_count
507 Contact: linux-pm@vger.kernel.org
509 Reports the number of full charge + discharge cycles the
510 battery has undergone.
515 Integer > 0: representing full cycles
516 Integer = 0: cycle_count info is not available
520 What: /sys/class/power_supply/<supply_name>/input_current_limit
522 Contact: linux-pm@vger.kernel.org
524 Details the incoming IBUS current limit currently set in the
525 supply. Normally this is configured based on the type of
526 connection made (e.g. A configured SDP should output a maximum
527 of 500mA so the input current limit is set to the same value).
528 Use preferably input_power_limit, and for problems that can be
529 solved using power limit use input_current_limit.
533 Valid values: Represented in microamps
535 What: /sys/class/power_supply/<supply_name>/input_voltage_limit
537 Contact: linux-pm@vger.kernel.org
539 This entry configures the incoming VBUS voltage limit currently
540 set in the supply. Normally this is configured based on
541 system-level knowledge or user input (e.g. This is part of the
542 Pixel C's thermal management strategy to effectively limit the
543 input power to 5V when the screen is on to meet Google's skin
544 temperature targets). Note that this feature should not be
545 used for safety critical things.
546 Use preferably input_power_limit, and for problems that can be
547 solved using power limit use input_voltage_limit.
551 Valid values: Represented in microvolts
553 What: /sys/class/power_supply/<supply_name>/input_power_limit
555 Contact: linux-pm@vger.kernel.org
557 This entry configures the incoming power limit currently set
558 in the supply. Normally this is configured based on
559 system-level knowledge or user input. Use preferably this
560 feature to limit the incoming power and use current/voltage
561 limit only for problems that can be solved using power limit.
565 Valid values: Represented in microwatts
567 What: /sys/class/power_supply/<supply_name>/online,
569 Contact: linux-pm@vger.kernel.org
571 Indicates if VBUS is present for the supply. When the supply is
572 online, and the supply allows it, then it's possible to switch
573 between online states (e.g. Fixed -> Programmable for a PD_PPS
574 USB supply so voltage and current can be controlled).
580 == ==================================================
582 1: Online Fixed - Fixed Voltage Supply
583 2: Online Programmable - Programmable Voltage Supply
584 == ==================================================
586 What: /sys/class/power_supply/<supply_name>/usb_type
588 Contact: linux-pm@vger.kernel.org
590 Reports what type of USB connection is currently active for
591 the supply, for example it can show if USB-PD capable source
597 "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
598 "PD_DRP", "PD_PPS", "BrickID"
600 **Device Specific Properties**
602 What: /sys/class/power/ds2760-battery.*/charge_now
604 KernelVersion: 2.6.35
605 Contact: Daniel Mack <daniel@caiaq.de>
607 This file is writeable and can be used to set the current
608 coloumb counter value inside the battery monitor chip. This
609 is needed for unavoidable corrections of aging batteries.
610 A userspace daemon can monitor the battery charging logic
611 and once the counter drops out of considerable bounds, take
614 What: /sys/class/power/ds2760-battery.*/charge_full
616 KernelVersion: 2.6.35
617 Contact: Daniel Mack <daniel@caiaq.de>
619 This file is writeable and can be used to set the assumed
620 battery 'full level'. As batteries age, this value has to be
623 What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
625 KernelVersion: 3.18.0
626 Contact: Krzysztof Kozlowski <krzk@kernel.org>
628 This entry shows and sets the maximum time the max14577
629 charger operates in fast-charge mode. When the timer expires
630 the device will terminate fast-charge mode (charging current
631 will drop to 0 A) and will trigger interrupt.
638 What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer
640 KernelVersion: 3.19.0
641 Contact: Krzysztof Kozlowski <krzk@kernel.org>
643 This entry shows and sets the maximum time the max77693
644 charger operates in fast-charge mode. When the timer expires
645 the device will terminate fast-charge mode (charging current
646 will drop to 0 A) and will trigger interrupt.
650 - 4 - 16 (hours), step by 2 (rounded down)
653 What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
655 KernelVersion: 3.19.0
656 Contact: Krzysztof Kozlowski <krzk@kernel.org>
658 This entry shows and sets the charging current threshold for
659 entering top-off charging mode. When charging current in fast
660 charge mode drops below this value, the charger will trigger
661 interrupt and start top-off charging mode.
665 - 100000 - 200000 (microamps), step by 25000 (rounded down)
666 - 200000 - 350000 (microamps), step by 50000 (rounded down)
669 What: /sys/class/power_supply/max77693-charger/device/top_off_timer
671 KernelVersion: 3.19.0
672 Contact: Krzysztof Kozlowski <krzk@kernel.org>
674 This entry shows and sets the maximum time the max77693
675 charger operates in top-off charge mode. When the timer expires
676 the device will terminate top-off charge mode (charging current
677 will drop to 0 A) and will trigger interrupt.
681 - 0 - 70 (minutes), step by 10 (rounded down)
683 What: /sys/class/power_supply/bq24257-charger/ovp_voltage
686 Contact: Andreas Dannenberg <dannenberg@ti.com>
688 This entry configures the overvoltage protection feature of bq24257-
689 type charger devices. This feature protects the device and other
690 components against damage from overvoltage on the input supply. See
691 device datasheet for details.
695 - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
698 What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage
701 Contact: Andreas Dannenberg <dannenberg@ti.com>
703 This entry configures the input dynamic power path management voltage of
704 bq24257-type charger devices. Once the supply drops to the configured
705 voltage, the input current limit is reduced down to prevent the further
706 drop of the supply. When the IC enters this mode, the charge current is
707 lower than the set value. See device datasheet for details.
711 - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
714 What: /sys/class/power_supply/bq24257-charger/high_impedance_enable
717 Contact: Andreas Dannenberg <dannenberg@ti.com>
719 This entry allows enabling the high-impedance mode of bq24257-type
720 charger devices. If enabled, it places the charger IC into low power
721 standby mode with the switch mode controller disabled. When disabled,
722 the charger operates normally. See device datasheet for details.
729 What: /sys/class/power_supply/bq24257-charger/sysoff_enable
732 Contact: Andreas Dannenberg <dannenberg@ti.com>
734 This entry allows enabling the sysoff mode of bq24257-type charger
735 devices. If enabled and the input is removed, the internal battery FET
736 is turned off in order to reduce the leakage from the BAT pin to less
737 than 1uA. Note that on some devices/systems this disconnects the battery
738 from the system. See device datasheet for details.
745 What: /sys/class/power_supply/<supply_name>/manufacture_year
747 Contact: linux-pm@vger.kernel.org
749 Reports the year (following Gregorian calendar) when the device has been
754 Valid values: Reported as integer
756 What: /sys/class/power_supply/<supply_name>/manufacture_month
758 Contact: linux-pm@vger.kernel.org
760 Reports the month when the device has been manufactured.
766 What: /sys/class/power_supply/<supply_name>/manufacture_day
768 Contact: linux-pm@vger.kernel.org
770 Reports the day of month when the device has been manufactured.