xref: /linux/Documentation/ABI/testing/sysfs-class-power (revision 1193e205dbb6feca917dc8e1862ffcdf2194234b)
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
556**USB Properties**
557
558What:		/sys/class/power_supply/<supply_name>/input_current_limit
559Date:		July 2014
560Contact:	linux-pm@vger.kernel.org
561Description:
562		Details the incoming IBUS current limit currently set in the
563		supply. Normally this is configured based on the type of
564		connection made (e.g. A configured SDP should output a maximum
565		of 500mA so the input current limit is set to the same value).
566		Use preferably input_power_limit, and for problems that can be
567		solved using power limit use input_current_limit.
568
569		Access: Read, Write
570
571		Valid values: Represented in microamps
572
573What:		/sys/class/power_supply/<supply_name>/input_voltage_limit
574Date:		May 2019
575Contact:	linux-pm@vger.kernel.org
576Description:
577		This entry configures the incoming VBUS voltage limit currently
578		set in the supply. Normally this is configured based on
579		system-level knowledge or user input (e.g. This is part of the
580		Pixel C's thermal management strategy to effectively limit the
581		input power to 5V when the screen is on to meet Google's skin
582		temperature targets). Note that this feature should not be
583		used for safety critical things.
584		Use preferably input_power_limit, and for problems that can be
585		solved using power limit use input_voltage_limit.
586
587		Access: Read, Write
588
589		Valid values: Represented in microvolts
590
591What:		/sys/class/power_supply/<supply_name>/input_power_limit
592Date:		May 2019
593Contact:	linux-pm@vger.kernel.org
594Description:
595		This entry configures the incoming power limit currently set
596		in the supply. Normally this is configured based on
597		system-level knowledge or user input. Use preferably this
598		feature to limit the incoming power and use current/voltage
599		limit only for problems that can be solved using power limit.
600
601		Access: Read, Write
602
603		Valid values: Represented in microwatts
604
605What:		/sys/class/power_supply/<supply_name>/online,
606Date:		May 2007
607Contact:	linux-pm@vger.kernel.org
608Description:
609		Indicates if VBUS is present for the supply. When the supply is
610		online, and the supply allows it, then it's possible to switch
611		between online states (e.g. Fixed -> Programmable for a PD_PPS
612		USB supply so voltage and current can be controlled).
613
614		Access: Read, Write
615
616		Valid values:
617
618			== ==================================================
619			0: Offline
620			1: Online Fixed - Fixed Voltage Supply
621			2: Online Programmable - Programmable Voltage Supply
622			== ==================================================
623
624What: 		/sys/class/power_supply/<supply_name>/usb_type
625Date:		March 2018
626Contact:	linux-pm@vger.kernel.org
627Description:
628		Reports what type of USB connection is currently active for
629		the supply, for example it can show if USB-PD capable source
630		is attached.
631
632		Access: For power-supplies which consume USB power such
633		as battery charger chips, this indicates the type of
634		the connected USB power source and is Read-Only.
635
636		For power-supplies which act as a USB power-source such as
637		e.g. the UCS1002 USB Port Power Controller this is writable.
638
639		Valid values:
640			      "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
641			      "PD_DRP", "PD_PPS", "BrickID"
642
643**Device Specific Properties**
644
645What:		/sys/class/power/ds2760-battery.*/charge_now
646Date:		May 2010
647KernelVersion:	2.6.35
648Contact:	Daniel Mack <daniel@caiaq.de>
649Description:
650		This file is writeable and can be used to set the current
651		coloumb counter value inside the battery monitor chip. This
652		is needed for unavoidable corrections of aging batteries.
653		A userspace daemon can monitor the battery charging logic
654		and once the counter drops out of considerable bounds, take
655		appropriate action.
656
657What:		/sys/class/power/ds2760-battery.*/charge_full
658Date:		May 2010
659KernelVersion:	2.6.35
660Contact:	Daniel Mack <daniel@caiaq.de>
661Description:
662		This file is writeable and can be used to set the assumed
663		battery 'full level'. As batteries age, this value has to be
664		amended over time.
665
666What:		/sys/class/power_supply/max14577-charger/device/fast_charge_timer
667Date:		October 2014
668KernelVersion:	3.18.0
669Contact:	Krzysztof Kozlowski <krzk@kernel.org>
670Description:
671		This entry shows and sets the maximum time the max14577
672		charger operates in fast-charge mode. When the timer expires
673		the device will terminate fast-charge mode (charging current
674		will drop to 0 A) and will trigger interrupt.
675
676		Valid values:
677
678		- 5, 6 or 7 (hours),
679		- 0: disabled.
680
681What:		/sys/class/power_supply/max77693-charger/device/fast_charge_timer
682Date:		January 2015
683KernelVersion:	3.19.0
684Contact:	Krzysztof Kozlowski <krzk@kernel.org>
685Description:
686		This entry shows and sets the maximum time the max77693
687		charger operates in fast-charge mode. When the timer expires
688		the device will terminate fast-charge mode (charging current
689		will drop to 0 A) and will trigger interrupt.
690
691		Valid values:
692
693		- 4 - 16 (hours), step by 2 (rounded down)
694		- 0: disabled.
695
696What:		/sys/class/power_supply/max77693-charger/device/top_off_threshold_current
697Date:		January 2015
698KernelVersion:	3.19.0
699Contact:	Krzysztof Kozlowski <krzk@kernel.org>
700Description:
701		This entry shows and sets the charging current threshold for
702		entering top-off charging mode. When charging current in fast
703		charge mode drops below this value, the charger will trigger
704		interrupt and start top-off charging mode.
705
706		Valid values:
707
708		- 100000 - 200000 (microamps), step by 25000 (rounded down)
709		- 200000 - 350000 (microamps), step by 50000 (rounded down)
710		- 0: disabled.
711
712What:		/sys/class/power_supply/max77693-charger/device/top_off_timer
713Date:		January 2015
714KernelVersion:	3.19.0
715Contact:	Krzysztof Kozlowski <krzk@kernel.org>
716Description:
717		This entry shows and sets the maximum time the max77693
718		charger operates in top-off charge mode. When the timer expires
719		the device will terminate top-off charge mode (charging current
720		will drop to 0 A) and will trigger interrupt.
721
722		Valid values:
723
724		- 0 - 70 (minutes), step by 10 (rounded down)
725
726What:		/sys/class/power_supply/bq24257-charger/ovp_voltage
727Date:		October 2015
728KernelVersion:	4.4.0
729Contact:	Andreas Dannenberg <dannenberg@ti.com>
730Description:
731		This entry configures the overvoltage protection feature of bq24257-
732		type charger devices. This feature protects the device and other
733		components against damage from overvoltage on the input supply. See
734		device datasheet for details.
735
736		Valid values:
737
738		- 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
739		  10500000 (all uV)
740
741What:		/sys/class/power_supply/bq24257-charger/in_dpm_voltage
742Date:		October 2015
743KernelVersion:	4.4.0
744Contact:	Andreas Dannenberg <dannenberg@ti.com>
745Description:
746		This entry configures the input dynamic power path management voltage of
747		bq24257-type charger devices. Once the supply drops to the configured
748		voltage, the input current limit is reduced down to prevent the further
749		drop of the supply. When the IC enters this mode, the charge current is
750		lower than the set value. See device datasheet for details.
751
752		Valid values:
753
754		- 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
755		  4760000 (all uV)
756
757What:		/sys/class/power_supply/bq24257-charger/high_impedance_enable
758Date:		October 2015
759KernelVersion:	4.4.0
760Contact:	Andreas Dannenberg <dannenberg@ti.com>
761Description:
762		This entry allows enabling the high-impedance mode of bq24257-type
763		charger devices. If enabled, it places the charger IC into low power
764		standby mode with the switch mode controller disabled. When disabled,
765		the charger operates normally. See device datasheet for details.
766
767		Valid values:
768
769		- 1: enabled
770		- 0: disabled
771
772What:		/sys/class/power_supply/bq24257-charger/sysoff_enable
773Date:		October 2015
774KernelVersion:	4.4.0
775Contact:	Andreas Dannenberg <dannenberg@ti.com>
776Description:
777		This entry allows enabling the sysoff mode of bq24257-type charger
778		devices. If enabled and the input is removed, the internal battery FET
779		is turned off in order to reduce the leakage from the BAT pin to less
780		than 1uA. Note that on some devices/systems this disconnects the battery
781		from the system. See device datasheet for details.
782
783		Valid values:
784
785		- 1: enabled
786		- 0: disabled
787
788What:		/sys/class/power_supply/<supply_name>/manufacture_year
789Date:		January 2020
790Contact:	linux-pm@vger.kernel.org
791Description:
792		Reports the year (following Gregorian calendar) when the device has been
793		manufactured.
794
795		Access: Read
796
797		Valid values: Reported as integer
798
799What:		/sys/class/power_supply/<supply_name>/manufacture_month
800Date:		January 2020
801Contact:	linux-pm@vger.kernel.org
802Description:
803		Reports the month when the device has been manufactured.
804
805		Access: Read
806
807		Valid values: 1-12
808
809What:		/sys/class/power_supply/<supply_name>/manufacture_day
810Date:		January 2020
811Contact:	linux-pm@vger.kernel.org
812Description:
813		Reports the day of month when the device has been manufactured.
814
815		Access: Read
816		Valid values: 1-31
817
818What:		/sys/class/power_supply/<supply_name>/extensions/<extension_name>
819Date:		March 2025
820Contact:	linux-pm@vger.kernel.org
821Description:
822		Reports the extensions registered to the power supply.
823		Each entry is a link to the device which registered the extension.
824
825		Access: Read
826
827What:		/sys/class/power_supply/max8971-charger/fast_charge_timer
828Date:		May 2025
829KernelVersion:	6.15.0
830Contact:	Svyatoslav Ryhel <clamor95@gmail.com>
831Description:
832		This entry shows and sets the maximum time the max8971
833		charger operates in fast-charge mode. When the timer expires
834		the device will terminate fast-charge mode (charging current
835		will drop to 0 A) and will trigger interrupt.
836
837		Valid values:
838
839		- 4 - 10 (hours), step by 1
840		- 0: disabled.
841
842What:		/sys/class/power_supply/max8971-charger/top_off_threshold_current
843Date:		May 2025
844KernelVersion:	6.15.0
845Contact:	Svyatoslav Ryhel <clamor95@gmail.com>
846Description:
847		This entry shows and sets the charging current threshold for
848		entering top-off charging mode. When charging current in fast
849		charge mode drops below this value, the charger will trigger
850		interrupt and start top-off charging mode.
851
852		Valid values:
853
854		- 50000 - 200000 (microamps), step by 50000 (rounded down)
855
856What:		/sys/class/power_supply/max8971-charger/top_off_timer
857Date:		May 2025
858KernelVersion:	6.15.0
859Contact:	Svyatoslav Ryhel <clamor95@gmail.com>
860Description:
861		This entry shows and sets the maximum time the max8971
862		charger operates in top-off charge mode. When the timer expires
863		the device will terminate top-off charge mode (charging current
864		will drop to 0 A) and will trigger interrupt.
865
866		Valid values:
867
868		- 0 - 70 (minutes), step by 10 (rounded down)
869