Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1**General Properties**
2
3What: /sys/class/power_supply/<supply_name>/manufacturer
4Date: May 2007
5Contact: linux-pm@vger.kernel.org
6Description:
7 Reports the name of the device manufacturer.
8
9 Access: Read
10 Valid values: Represented as string
11
12What: /sys/class/power_supply/<supply_name>/model_name
13Date: May 2007
14Contact: linux-pm@vger.kernel.org
15Description:
16 Reports the name of the device model.
17
18 Access: Read
19 Valid values: Represented as string
20
21What: /sys/class/power_supply/<supply_name>/serial_number
22Date: January 2008
23Contact: linux-pm@vger.kernel.org
24Description:
25 Reports the serial number of the device.
26
27 Access: Read
28 Valid values: Represented as string
29
30What: /sys/class/power_supply/<supply_name>/type
31Date: May 2010
32Contact: linux-pm@vger.kernel.org
33Description:
34 Describes the main type of the supply.
35
36 Access: Read
37 Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"
38
39**Battery and USB properties**
40
41What: /sys/class/power_supply/<supply_name>/current_avg
42Date: May 2007
43Contact: linux-pm@vger.kernel.org
44Description:
45 Battery:
46
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
50 value.
51
52 USB:
53
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.
57
58 Access: Read
59
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.
63
64What: /sys/class/power_supply/<supply_name>/current_max
65Date: October 2010
66Contact: linux-pm@vger.kernel.org
67Description:
68 Battery:
69
70 Reports the maximum IBAT current allowed into the battery.
71
72 USB:
73
74 Reports the maximum IBUS current the supply can support.
75
76 Access: Read
77 Valid values: Represented in microamps
78
79What: /sys/class/power_supply/<supply_name>/current_now
80Date: May 2007
81Contact: linux-pm@vger.kernel.org
82Description:
83
84 Battery:
85
86 Reports an instant, single IBAT current reading for the
87 battery. This value is not averaged/smoothed.
88
89 Access: Read
90
91 USB:
92
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.
97
98 Access: Read, Write
99
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.
103
104What: /sys/class/power_supply/<supply_name>/temp
105Date: May 2007
106Contact: linux-pm@vger.kernel.org
107Description:
108 Battery:
109
110 Reports the current TBAT battery temperature reading.
111
112 USB:
113
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)
117
118 Access: Read
119
120 Valid values: Represented in 1/10 Degrees Celsius
121
122What: /sys/class/power_supply/<supply_name>/temp_alert_max
123Date: July 2012
124Contact: linux-pm@vger.kernel.org
125Description:
126 Battery:
127
128 Maximum TBAT temperature trip-wire value where the supply will
129 notify user-space of the event.
130
131 USB:
132
133 Maximum supply temperature trip-wire value where the supply
134 will notify user-space of the event.
135
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
140 stopped).
141
142 Access: Read
143
144 Valid values: Represented in 1/10 Degrees Celsius
145
146What: /sys/class/power_supply/<supply_name>/temp_alert_min
147Date: July 2012
148Contact: linux-pm@vger.kernel.org
149Description:
150
151 Battery:
152
153 Minimum TBAT temperature trip-wire value where the supply will
154 notify user-space of the event.
155
156 USB:
157
158 Minimum supply temperature trip-wire value where the supply
159 will notify user-space of the event.
160
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).
166
167 Access: Read
168
169 Valid values: Represented in 1/10 Degrees Celsius
170
171What: /sys/class/power_supply/<supply_name>/temp_max
172Date: July 2014
173Contact: linux-pm@vger.kernel.org
174Description:
175 Battery:
176
177 Reports the maximum allowed TBAT battery temperature for
178 charging.
179
180 USB:
181
182 Reports the maximum allowed supply temperature for operation.
183
184 Access: Read
185
186 Valid values: Represented in 1/10 Degrees Celsius
187
188What: /sys/class/power_supply/<supply_name>/temp_min
189Date: July 2014
190Contact: linux-pm@vger.kernel.org
191Description:
192 Battery:
193
194 Reports the minimum allowed TBAT battery temperature for
195 charging.
196
197 USB:
198
199 Reports the minimum allowed supply temperature for operation.
200
201 Access: Read
202
203 Valid values: Represented in 1/10 Degrees Celsius
204
205What: /sys/class/power_supply/<supply_name>/voltage_max,
206Date: January 2008
207Contact: linux-pm@vger.kernel.org
208Description:
209 Battery:
210
211 Reports the maximum safe VBAT voltage permitted for the
212 battery, during charging.
213
214 USB:
215
216 Reports the maximum VBUS voltage the supply can support.
217
218 Access: Read
219
220 Valid values: Represented in microvolts
221
222What: /sys/class/power_supply/<supply_name>/voltage_min,
223Date: January 2008
224Contact: linux-pm@vger.kernel.org
225Description:
226 Battery:
227
228 Reports the minimum safe VBAT voltage permitted for the
229 battery, during discharging.
230
231 USB:
232
233 Reports the minimum VBUS voltage the supply can support.
234
235 Access: Read
236
237 Valid values: Represented in microvolts
238
239What: /sys/class/power_supply/<supply_name>/voltage_now,
240Date: May 2007
241Contact: linux-pm@vger.kernel.org
242Description:
243 Battery:
244
245 Reports an instant, single VBAT voltage reading for the
246 battery. This value is not averaged/smoothed.
247
248 Access: Read
249
250 USB:
251
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.
256
257 Access: Read, Write
258
259 Valid values: Represented in microvolts
260
261**Battery Properties**
262
263What: /sys/class/power_supply/<supply_name>/capacity
264Date: May 2007
265Contact: linux-pm@vger.kernel.org
266Description:
267 Fine grain representation of battery capacity.
268
269 Access: Read
270
271 Valid values: 0 - 100 (percent)
272
273What: /sys/class/power_supply/<supply_name>/capacity_alert_max
274Date: July 2012
275Contact: linux-pm@vger.kernel.org
276Description:
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
282 low).
283
284 Access: Read, Write
285
286 Valid values: 0 - 100 (percent)
287
288What: /sys/class/power_supply/<supply_name>/capacity_alert_min
289Date: July 2012
290Contact: linux-pm@vger.kernel.org
291Description:
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
297 critically low).
298
299 Access: Read, Write
300
301 Valid values: 0 - 100 (percent)
302
303What: /sys/class/power_supply/<supply_name>/capacity_error_margin
304Date: April 2019
305Contact: linux-pm@vger.kernel.org
306Description:
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
313 completely useless.
314
315 Access: Read
316
317 Valid values: 0 - 100 (percent)
318
319What: /sys/class/power_supply/<supply_name>/capacity_level
320Date: June 2009
321Contact: linux-pm@vger.kernel.org
322Description:
323 Coarse representation of battery capacity.
324
325 Access: Read
326
327 Valid values:
328 "Unknown", "Critical", "Low", "Normal", "High",
329 "Full"
330
331What: /sys/class/power_supply/<supply_name>/charge_control_limit
332Date: Oct 2012
333Contact: linux-pm@vger.kernel.org
334Description:
335 Maximum allowable charging current. Used for charge rate
336 throttling for thermal cooling or improving battery health.
337
338 Access: Read, Write
339
340 Valid values: Represented in microamps
341
342What: /sys/class/power_supply/<supply_name>/charge_control_limit_max
343Date: Oct 2012
344Contact: linux-pm@vger.kernel.org
345Description:
346 Maximum legal value for the charge_control_limit property.
347
348 Access: Read
349
350 Valid values: Represented in microamps
351
352What: /sys/class/power_supply/<supply_name>/charge_control_start_threshold
353Date: April 2019
354Contact: linux-pm@vger.kernel.org
355Description:
356 Represents a battery percentage level, below which charging will
357 begin.
358
359 Access: Read, Write
360 Valid values: 0 - 100 (percent)
361
362What: /sys/class/power_supply/<supply_name>/charge_control_end_threshold
363Date: April 2019
364Contact: linux-pm@vger.kernel.org
365Description:
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.
371
372 Access: Read, Write
373
374 Valid values: 0 - 100 (percent)
375
376What: /sys/class/power_supply/<supply_name>/charge_type
377Date: July 2009
378Contact: linux-pm@vger.kernel.org
379Description:
380 Select the charging algorithm to use for a battery.
381
382 Standard:
383 Fully charge the battery at a moderate rate.
384 Fast:
385 Quickly charge the battery using fast-charge
386 technology. This is typically harder on the battery
387 than standard charging and may lower its lifespan.
388 Trickle:
389 Users who primarily operate the system while
390 plugged into an external power source can extend
391 battery life with this mode. Vendor tooling may
392 call this "Primarily AC Use".
393 Adaptive:
394 Automatically optimize battery charge rate based
395 on typical usage pattern.
396 Custom:
397 Use the charge_control_* properties to determine
398 when to start and stop charging. Advanced users
399 can use this to drastically extend battery life.
400 Long Life:
401 The charger reduces its charging rate in order to
402 prolong the battery health.
403 Bypass:
404 The charger bypasses the charging path around the
405 integrated converter allowing for a "smart" wall
406 adaptor to perform the power conversion externally.
407
408 Access: Read, Write
409
410 Reading this returns the current active value, e.g. 'Standard'.
411 Check charge_types to get the values supported by the battery.
412
413 Valid values:
414 "Unknown", "N/A", "Trickle", "Fast", "Standard",
415 "Adaptive", "Custom", "Long Life", "Bypass"
416
417What: /sys/class/power_supply/<supply_name>/charge_types
418Date: December 2024
419Contact: linux-pm@vger.kernel.org
420Description:
421 Identical to charge_type but reading returns a list of supported
422 charge-types with the currently active type surrounded by square
423 brackets, e.g.: "Fast [Standard] Long_Life".
424
425 power_supply class devices may support both charge_type and
426 charge_types for backward compatibility. In this case both will
427 always have the same active value and the active value can be
428 changed by writing either property.
429
430 Note charge-types which contain a space such as "Long Life" will
431 have the space replaced by a '_' resulting in e.g. "Long_Life".
432 When writing charge-types both variants are accepted.
433
434What: /sys/class/power_supply/<supply_name>/charge_term_current
435Date: July 2014
436Contact: linux-pm@vger.kernel.org
437Description:
438 Reports the charging current value which is used to determine
439 when the battery is considered full and charging should end.
440
441 Access: Read
442
443 Valid values: Represented in microamps
444
445What: /sys/class/power_supply/<supply_name>/health
446Date: May 2007
447Contact: linux-pm@vger.kernel.org
448Description:
449 Reports the health of the battery or battery side of charger
450 functionality.
451
452 Access: Read
453
454 Valid values:
455 "Unknown", "Good", "Overheat", "Dead",
456 "Over voltage", "Under voltage", "Unspecified failure", "Cold",
457 "Watchdog timer expire", "Safety timer expire",
458 "Over current", "Calibration required", "Warm",
459 "Cool", "Hot", "No battery", "Blown fuse", "Cell imbalance"
460
461What: /sys/class/power_supply/<supply_name>/precharge_current
462Date: June 2017
463Contact: linux-pm@vger.kernel.org
464Description:
465 Reports the charging current applied during pre-charging phase
466 for a battery charge cycle.
467
468 Access: Read
469
470 Valid values: Represented in microamps
471
472What: /sys/class/power_supply/<supply_name>/present
473Date: May 2007
474Contact: linux-pm@vger.kernel.org
475Description:
476 Reports whether a battery is present or not in the system. If the
477 property does not exist, the battery is considered to be present.
478
479 Access: Read
480
481 Valid values:
482
483 == =======
484 0: Absent
485 1: Present
486 == =======
487
488What: /sys/class/power_supply/<supply_name>/status
489Date: May 2007
490Contact: linux-pm@vger.kernel.org
491Description:
492 Represents the charging status of the battery. Normally this
493 is read-only reporting although for some supplies this can be
494 used to enable/disable charging to the battery.
495
496 Access: Read, Write
497
498 Valid values:
499 "Unknown", "Charging", "Discharging",
500 "Not charging", "Full"
501
502What: /sys/class/power_supply/<supply_name>/charge_behaviour
503Date: November 2021
504Contact: linux-pm@vger.kernel.org
505Description:
506 Represents the charging behaviour.
507
508 Access: Read, Write
509
510 Valid values:
511 ===================== ========================================
512 auto: Charge normally, respect thresholds
513 inhibit-charge: Do not charge while AC is attached
514 inhibit-charge-awake: inhibit-charge only when device is awake
515 force-discharge: Force discharge while AC is attached
516 ===================== ========================================
517
518What: /sys/class/power_supply/<supply_name>/technology
519Date: May 2007
520Contact: linux-pm@vger.kernel.org
521Description:
522 Describes the battery technology supported by the supply.
523
524 Access: Read
525
526 Valid values:
527 "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
528 "NiCd", "LiMn"
529
530
531What: /sys/class/power_supply/<supply_name>/voltage_avg,
532Date: May 2007
533Contact: linux-pm@vger.kernel.org
534Description:
535 Reports an average VBAT voltage reading for the battery, over a
536 fixed period. Normally devices will provide a fixed interval in
537 which they average readings to smooth out the reported value.
538
539 Access: Read
540
541 Valid values: Represented in microvolts
542
543What: /sys/class/power_supply/<supply_name>/cycle_count
544Date: January 2010
545Contact: linux-pm@vger.kernel.org
546Description:
547 Reports the number of full charge + discharge cycles the
548 battery has undergone.
549
550 Access: Read
551
552 Valid values:
553 Integer > 0: representing full cycles
554 Integer = 0: cycle_count info is not available
555
556What: /sys/class/power_supply/<supply_name>/internal_resistance
557Date: August 2025
558Contact: linux-arm-msm@vger.kernel.org
559Description:
560 Represent the battery's internal resistance, often referred
561 to as Equivalent Series Resistance (ESR). It is a dynamic
562 parameter that reflects the opposition to current flow within
563 the cell. It is not a fixed value but varies significantly
564 based on several operational conditions, including battery
565 state of charge (SoC), temperature, and whether the battery
566 is in a charging or discharging state.
567
568 Access: Read
569
570 Valid values: Represented in microohms
571
572What: /sys/class/power_supply/<supply_name>/state_of_health
573Date: August 2025
574Contact: linux-arm-msm@vger.kernel.org
575Description:
576 The state_of_health parameter quantifies the overall condition
577 of a battery as a percentage, reflecting its ability to deliver
578 rated performance relative to its original specifications. It is
579 dynamically computed using a combination of learned capacity
580 and impedance-based degradation indicators, both of which evolve
581 over the battery's lifecycle.
582 Note that the exact algorithms are kept secret by most battery
583 vendors and the value from different battery vendors cannot be
584 compared with each other as there is no vendor-agnostic definition
585 of "performance". Also this usually cannot be used for any
586 calculations (i.e. this is not the factor between charge_full and
587 charge_full_design).
588
589 Access: Read
590
591 Valid values: 0 - 100 (percent)
592
593**USB Properties**
594
595What: /sys/class/power_supply/<supply_name>/input_current_limit
596Date: July 2014
597Contact: linux-pm@vger.kernel.org
598Description:
599 Details the incoming IBUS current limit currently set in the
600 supply. Normally this is configured based on the type of
601 connection made (e.g. A configured SDP should output a maximum
602 of 500mA so the input current limit is set to the same value).
603 Use preferably input_power_limit, and for problems that can be
604 solved using power limit use input_current_limit.
605
606 Access: Read, Write
607
608 Valid values: Represented in microamps
609
610What: /sys/class/power_supply/<supply_name>/input_voltage_limit
611Date: May 2019
612Contact: linux-pm@vger.kernel.org
613Description:
614 This entry configures the incoming VBUS voltage limit currently
615 set in the supply. Normally this is configured based on
616 system-level knowledge or user input (e.g. This is part of the
617 Pixel C's thermal management strategy to effectively limit the
618 input power to 5V when the screen is on to meet Google's skin
619 temperature targets). Note that this feature should not be
620 used for safety critical things.
621 Use preferably input_power_limit, and for problems that can be
622 solved using power limit use input_voltage_limit.
623
624 Access: Read, Write
625
626 Valid values: Represented in microvolts
627
628What: /sys/class/power_supply/<supply_name>/input_power_limit
629Date: May 2019
630Contact: linux-pm@vger.kernel.org
631Description:
632 This entry configures the incoming power limit currently set
633 in the supply. Normally this is configured based on
634 system-level knowledge or user input. Use preferably this
635 feature to limit the incoming power and use current/voltage
636 limit only for problems that can be solved using power limit.
637
638 Access: Read, Write
639
640 Valid values: Represented in microwatts
641
642What: /sys/class/power_supply/<supply_name>/online,
643Date: May 2007
644Contact: linux-pm@vger.kernel.org
645Description:
646 Indicates if VBUS is present for the supply. When the supply is
647 online, and the supply allows it, then it's possible to switch
648 between online states (e.g. Fixed -> Programmable for a PD_PPS
649 USB supply so voltage and current can be controlled).
650
651 Access: Read, Write
652
653 Valid values:
654
655 == ==================================================
656 0: Offline
657 1: Online Fixed - Fixed Voltage Supply
658 2: Online Programmable - Programmable Voltage Supply
659 == ==================================================
660
661What: /sys/class/power_supply/<supply_name>/usb_type
662Date: March 2018
663Contact: linux-pm@vger.kernel.org
664Description:
665 Reports what type of USB connection is currently active for
666 the supply, for example it can show if USB-PD capable source
667 is attached.
668
669 Access: For power-supplies which consume USB power such
670 as battery charger chips, this indicates the type of
671 the connected USB power source and is Read-Only.
672
673 For power-supplies which act as a USB power-source such as
674 e.g. the UCS1002 USB Port Power Controller this is writable.
675
676 Valid values:
677 "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
678 "PD_DRP", "PD_PPS", "BrickID"
679
680**Device Specific Properties**
681
682What: /sys/class/power/ds2760-battery.*/charge_now
683Date: May 2010
684KernelVersion: 2.6.35
685Contact: Daniel Mack <daniel@caiaq.de>
686Description:
687 This file is writeable and can be used to set the current
688 coloumb counter value inside the battery monitor chip. This
689 is needed for unavoidable corrections of aging batteries.
690 A userspace daemon can monitor the battery charging logic
691 and once the counter drops out of considerable bounds, take
692 appropriate action.
693
694What: /sys/class/power/ds2760-battery.*/charge_full
695Date: May 2010
696KernelVersion: 2.6.35
697Contact: Daniel Mack <daniel@caiaq.de>
698Description:
699 This file is writeable and can be used to set the assumed
700 battery 'full level'. As batteries age, this value has to be
701 amended over time.
702
703What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
704Date: October 2014
705KernelVersion: 3.18.0
706Contact: Krzysztof Kozlowski <krzk@kernel.org>
707Description:
708 This entry shows and sets the maximum time the max14577
709 charger operates in fast-charge mode. When the timer expires
710 the device will terminate fast-charge mode (charging current
711 will drop to 0 A) and will trigger interrupt.
712
713 Valid values:
714
715 - 5, 6 or 7 (hours),
716 - 0: disabled.
717
718What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer
719Date: January 2015
720KernelVersion: 3.19.0
721Contact: Krzysztof Kozlowski <krzk@kernel.org>
722Description:
723 This entry shows and sets the maximum time the max77693
724 charger operates in fast-charge mode. When the timer expires
725 the device will terminate fast-charge mode (charging current
726 will drop to 0 A) and will trigger interrupt.
727
728 Valid values:
729
730 - 4 - 16 (hours), step by 2 (rounded down)
731 - 0: disabled.
732
733What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
734Date: January 2015
735KernelVersion: 3.19.0
736Contact: Krzysztof Kozlowski <krzk@kernel.org>
737Description:
738 This entry shows and sets the charging current threshold for
739 entering top-off charging mode. When charging current in fast
740 charge mode drops below this value, the charger will trigger
741 interrupt and start top-off charging mode.
742
743 Valid values:
744
745 - 100000 - 200000 (microamps), step by 25000 (rounded down)
746 - 200000 - 350000 (microamps), step by 50000 (rounded down)
747 - 0: disabled.
748
749What: /sys/class/power_supply/max77693-charger/device/top_off_timer
750Date: January 2015
751KernelVersion: 3.19.0
752Contact: Krzysztof Kozlowski <krzk@kernel.org>
753Description:
754 This entry shows and sets the maximum time the max77693
755 charger operates in top-off charge mode. When the timer expires
756 the device will terminate top-off charge mode (charging current
757 will drop to 0 A) and will trigger interrupt.
758
759 Valid values:
760
761 - 0 - 70 (minutes), step by 10 (rounded down)
762
763What: /sys/class/power_supply/bq24257-charger/ovp_voltage
764Date: October 2015
765KernelVersion: 4.4.0
766Contact: Andreas Dannenberg <dannenberg@ti.com>
767Description:
768 This entry configures the overvoltage protection feature of bq24257-
769 type charger devices. This feature protects the device and other
770 components against damage from overvoltage on the input supply. See
771 device datasheet for details.
772
773 Valid values:
774
775 - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
776 10500000 (all uV)
777
778What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage
779Date: October 2015
780KernelVersion: 4.4.0
781Contact: Andreas Dannenberg <dannenberg@ti.com>
782Description:
783 This entry configures the input dynamic power path management voltage of
784 bq24257-type charger devices. Once the supply drops to the configured
785 voltage, the input current limit is reduced down to prevent the further
786 drop of the supply. When the IC enters this mode, the charge current is
787 lower than the set value. See device datasheet for details.
788
789 Valid values:
790
791 - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
792 4760000 (all uV)
793
794What: /sys/class/power_supply/bq24257-charger/high_impedance_enable
795Date: October 2015
796KernelVersion: 4.4.0
797Contact: Andreas Dannenberg <dannenberg@ti.com>
798Description:
799 This entry allows enabling the high-impedance mode of bq24257-type
800 charger devices. If enabled, it places the charger IC into low power
801 standby mode with the switch mode controller disabled. When disabled,
802 the charger operates normally. See device datasheet for details.
803
804 Valid values:
805
806 - 1: enabled
807 - 0: disabled
808
809What: /sys/class/power_supply/bq24257-charger/sysoff_enable
810Date: October 2015
811KernelVersion: 4.4.0
812Contact: Andreas Dannenberg <dannenberg@ti.com>
813Description:
814 This entry allows enabling the sysoff mode of bq24257-type charger
815 devices. If enabled and the input is removed, the internal battery FET
816 is turned off in order to reduce the leakage from the BAT pin to less
817 than 1uA. Note that on some devices/systems this disconnects the battery
818 from the system. See device datasheet for details.
819
820 Valid values:
821
822 - 1: enabled
823 - 0: disabled
824
825What: /sys/class/power_supply/<supply_name>/manufacture_year
826Date: January 2020
827Contact: linux-pm@vger.kernel.org
828Description:
829 Reports the year (following Gregorian calendar) when the device has been
830 manufactured.
831
832 Access: Read
833
834 Valid values: Reported as integer
835
836What: /sys/class/power_supply/<supply_name>/manufacture_month
837Date: January 2020
838Contact: linux-pm@vger.kernel.org
839Description:
840 Reports the month when the device has been manufactured.
841
842 Access: Read
843
844 Valid values: 1-12
845
846What: /sys/class/power_supply/<supply_name>/manufacture_day
847Date: January 2020
848Contact: linux-pm@vger.kernel.org
849Description:
850 Reports the day of month when the device has been manufactured.
851
852 Access: Read
853 Valid values: 1-31
854
855What: /sys/class/power_supply/<supply_name>/extensions/<extension_name>
856Date: March 2025
857Contact: linux-pm@vger.kernel.org
858Description:
859 Reports the extensions registered to the power supply.
860 Each entry is a link to the device which registered the extension.
861
862 Access: Read
863
864What: /sys/class/power_supply/max8971-charger/fast_charge_timer
865Date: May 2025
866KernelVersion: 6.15.0
867Contact: Svyatoslav Ryhel <clamor95@gmail.com>
868Description:
869 This entry shows and sets the maximum time the max8971
870 charger operates in fast-charge mode. When the timer expires
871 the device will terminate fast-charge mode (charging current
872 will drop to 0 A) and will trigger interrupt.
873
874 Valid values:
875
876 - 4 - 10 (hours), step by 1
877 - 0: disabled.
878
879What: /sys/class/power_supply/max8971-charger/top_off_threshold_current
880Date: May 2025
881KernelVersion: 6.15.0
882Contact: Svyatoslav Ryhel <clamor95@gmail.com>
883Description:
884 This entry shows and sets the charging current threshold for
885 entering top-off charging mode. When charging current in fast
886 charge mode drops below this value, the charger will trigger
887 interrupt and start top-off charging mode.
888
889 Valid values:
890
891 - 50000 - 200000 (microamps), step by 50000 (rounded down)
892
893What: /sys/class/power_supply/max8971-charger/top_off_timer
894Date: May 2025
895KernelVersion: 6.15.0
896Contact: Svyatoslav Ryhel <clamor95@gmail.com>
897Description:
898 This entry shows and sets the maximum time the max8971
899 charger operates in top-off charge mode. When the timer expires
900 the device will terminate top-off charge mode (charging current
901 will drop to 0 A) and will trigger interrupt.
902
903 Valid values:
904
905 - 0 - 70 (minutes), step by 10 (rounded down)