drm/panel: panel-himax-hx83102: support for csot-pna957qt1-1 MIPI-DSI panel
[drm/drm-misc.git] / Documentation / ABI / testing / sysfs-class-power
blob2a5c1a09a28f91beec6b18ca7b4492093026bc81
1 **General Properties**
3 What:           /sys/class/power_supply/<supply_name>/manufacturer
4 Date:           May 2007
5 Contact:        linux-pm@vger.kernel.org
6 Description:
7                 Reports the name of the device manufacturer.
9                 Access: Read
10                 Valid values: Represented as string
12 What:           /sys/class/power_supply/<supply_name>/model_name
13 Date:           May 2007
14 Contact:        linux-pm@vger.kernel.org
15 Description:
16                 Reports the name of the device model.
18                 Access: Read
19                 Valid values: Represented as string
21 What:           /sys/class/power_supply/<supply_name>/serial_number
22 Date:           January 2008
23 Contact:        linux-pm@vger.kernel.org
24 Description:
25                 Reports the serial number of the device.
27                 Access: Read
28                 Valid values: Represented as string
30 What:           /sys/class/power_supply/<supply_name>/type
31 Date:           May 2010
32 Contact:        linux-pm@vger.kernel.org
33 Description:
34                 Describes the main type of the supply.
36                 Access: Read
37                 Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"
39 **Battery and USB properties**
41 What:           /sys/class/power_supply/<supply_name>/current_avg
42 Date:           May 2007
43 Contact:        linux-pm@vger.kernel.org
44 Description:
45                 Battery:
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.
52                 USB:
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.
58                 Access: Read
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
65 Date:           October 2010
66 Contact:        linux-pm@vger.kernel.org
67 Description:
68                 Battery:
70                   Reports the maximum IBAT current allowed into the battery.
72                 USB:
74                   Reports the maximum IBUS current the supply can support.
76                 Access: Read
77                 Valid values: Represented in microamps
79 What:           /sys/class/power_supply/<supply_name>/current_now
80 Date:           May 2007
81 Contact:        linux-pm@vger.kernel.org
82 Description:
84                 Battery:
86                   Reports an instant, single IBAT current reading for the
87                   battery. This value is not averaged/smoothed.
89                   Access: Read
91                 USB:
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.
98                   Access: Read, Write
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
105 Date:           May 2007
106 Contact:        linux-pm@vger.kernel.org
107 Description:
108                 Battery:
110                   Reports the current TBAT battery temperature reading.
112                 USB:
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)
118                 Access: Read
120                 Valid values: Represented in 1/10 Degrees Celsius
122 What:           /sys/class/power_supply/<supply_name>/temp_alert_max
123 Date:           July 2012
124 Contact:        linux-pm@vger.kernel.org
125 Description:
126                 Battery:
128                   Maximum TBAT temperature trip-wire value where the supply will
129                   notify user-space of the event.
131                 USB:
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
140                 stopped).
142                 Access: Read
144                 Valid values: Represented in 1/10 Degrees Celsius
146 What:           /sys/class/power_supply/<supply_name>/temp_alert_min
147 Date:           July 2012
148 Contact:        linux-pm@vger.kernel.org
149 Description:
151                 Battery:
153                   Minimum TBAT temperature trip-wire value where the supply will
154                   notify user-space of the event.
156                 USB:
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).
167                 Access: Read
169                 Valid values: Represented in 1/10 Degrees Celsius
171 What:           /sys/class/power_supply/<supply_name>/temp_max
172 Date:           July 2014
173 Contact:        linux-pm@vger.kernel.org
174 Description:
175                 Battery:
177                   Reports the maximum allowed TBAT battery temperature for
178                   charging.
180                 USB:
182                   Reports the maximum allowed supply temperature for operation.
184                 Access: Read
186                 Valid values: Represented in 1/10 Degrees Celsius
188 What:           /sys/class/power_supply/<supply_name>/temp_min
189 Date:           July 2014
190 Contact:        linux-pm@vger.kernel.org
191 Description:
192                 Battery:
194                   Reports the minimum allowed TBAT battery temperature for
195                   charging.
197                 USB:
199                   Reports the minimum allowed supply temperature for operation.
201                 Access: Read
203                 Valid values: Represented in 1/10 Degrees Celsius
205 What:           /sys/class/power_supply/<supply_name>/voltage_max,
206 Date:           January 2008
207 Contact:        linux-pm@vger.kernel.org
208 Description:
209                 Battery:
211                   Reports the maximum safe VBAT voltage permitted for the
212                   battery, during charging.
214                 USB:
216                   Reports the maximum VBUS voltage the supply can support.
218                 Access: Read
220                 Valid values: Represented in microvolts
222 What:           /sys/class/power_supply/<supply_name>/voltage_min,
223 Date:           January 2008
224 Contact:        linux-pm@vger.kernel.org
225 Description:
226                 Battery:
228                   Reports the minimum safe VBAT voltage permitted for the
229                   battery, during discharging.
231                 USB:
233                   Reports the minimum VBUS voltage the supply can support.
235                 Access: Read
237                 Valid values: Represented in microvolts
239 What:           /sys/class/power_supply/<supply_name>/voltage_now,
240 Date:           May 2007
241 Contact:        linux-pm@vger.kernel.org
242 Description:
243                 Battery:
245                   Reports an instant, single VBAT voltage reading for the
246                   battery. This value is not averaged/smoothed.
248                   Access: Read
250                 USB:
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.
257                   Access: Read, Write
259                 Valid values: Represented in microvolts
261 **Battery Properties**
263 What:           /sys/class/power_supply/<supply_name>/capacity
264 Date:           May 2007
265 Contact:        linux-pm@vger.kernel.org
266 Description:
267                 Fine grain representation of battery capacity.
269                 Access: Read
271                 Valid values: 0 - 100 (percent)
273 What:           /sys/class/power_supply/<supply_name>/capacity_alert_max
274 Date:           July 2012
275 Contact:        linux-pm@vger.kernel.org
276 Description:
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).
284                 Access: Read, Write
286                 Valid values: 0 - 100 (percent)
288 What:           /sys/class/power_supply/<supply_name>/capacity_alert_min
289 Date:           July 2012
290 Contact:        linux-pm@vger.kernel.org
291 Description:
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).
299                 Access: Read, Write
301                 Valid values: 0 - 100 (percent)
303 What:           /sys/class/power_supply/<supply_name>/capacity_error_margin
304 Date:           April 2019
305 Contact:        linux-pm@vger.kernel.org
306 Description:
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.
315                 Access: Read
317                 Valid values: 0 - 100 (percent)
319 What:           /sys/class/power_supply/<supply_name>/capacity_level
320 Date:           June 2009
321 Contact:        linux-pm@vger.kernel.org
322 Description:
323                 Coarse representation of battery capacity.
325                 Access: Read
327                 Valid values:
328                               "Unknown", "Critical", "Low", "Normal", "High",
329                               "Full"
331 What:           /sys/class/power_supply/<supply_name>/charge_control_limit
332 Date:           Oct 2012
333 Contact:        linux-pm@vger.kernel.org
334 Description:
335                 Maximum allowable charging current. Used for charge rate
336                 throttling for thermal cooling or improving battery health.
338                 Access: Read, Write
340                 Valid values: Represented in microamps
342 What:           /sys/class/power_supply/<supply_name>/charge_control_limit_max
343 Date:           Oct 2012
344 Contact:        linux-pm@vger.kernel.org
345 Description:
346                 Maximum legal value for the charge_control_limit property.
348                 Access: Read
350                 Valid values: Represented in microamps
352 What:           /sys/class/power_supply/<supply_name>/charge_control_start_threshold
353 Date:           April 2019
354 Contact:        linux-pm@vger.kernel.org
355 Description:
356                 Represents a battery percentage level, below which charging will
357                 begin.
359                 Access: Read, Write
360                 Valid values: 0 - 100 (percent)
362 What:           /sys/class/power_supply/<supply_name>/charge_control_end_threshold
363 Date:           April 2019
364 Contact:        linux-pm@vger.kernel.org
365 Description:
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.
372                 Access: Read, Write
374                 Valid values: 0 - 100 (percent)
376 What:           /sys/class/power_supply/<supply_name>/charge_type
377 Date:           July 2009
378 Contact:        linux-pm@vger.kernel.org
379 Description:
380                 Select the charging algorithm to use for a battery.
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.
408                 Access: Read, Write
410                 Reading this returns the current active value, e.g. 'Standard'.
411                 Check charge_types to get the values supported by the battery.
413                 Valid values:
414                               "Unknown", "N/A", "Trickle", "Fast", "Standard",
415                               "Adaptive", "Custom", "Long Life", "Bypass"
417 What:           /sys/class/power_supply/<supply_name>/charge_types
418 Date:           December 2024
419 Contact:        linux-pm@vger.kernel.org
420 Description:
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".
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.
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.
434 What:           /sys/class/power_supply/<supply_name>/charge_term_current
435 Date:           July 2014
436 Contact:        linux-pm@vger.kernel.org
437 Description:
438                 Reports the charging current value which is used to determine
439                 when the battery is considered full and charging should end.
441                 Access: Read
443                 Valid values: Represented in microamps
445 What:           /sys/class/power_supply/<supply_name>/health
446 Date:           May 2007
447 Contact:        linux-pm@vger.kernel.org
448 Description:
449                 Reports the health of the battery or battery side of charger
450                 functionality.
452                 Access: Read
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"
461 What:           /sys/class/power_supply/<supply_name>/precharge_current
462 Date:           June 2017
463 Contact:        linux-pm@vger.kernel.org
464 Description:
465                 Reports the charging current applied during pre-charging phase
466                 for a battery charge cycle.
468                 Access: Read
470                 Valid values: Represented in microamps
472 What:           /sys/class/power_supply/<supply_name>/present
473 Date:           May 2007
474 Contact:        linux-pm@vger.kernel.org
475 Description:
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.
479                 Access: Read
481                 Valid values:
483                         == =======
484                         0: Absent
485                         1: Present
486                         == =======
488 What:           /sys/class/power_supply/<supply_name>/status
489 Date:           May 2007
490 Contact:        linux-pm@vger.kernel.org
491 Description:
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.
496                 Access: Read, Write
498                 Valid values:
499                               "Unknown", "Charging", "Discharging",
500                               "Not charging", "Full"
502 What:           /sys/class/power_supply/<supply_name>/charge_behaviour
503 Date:           November 2021
504 Contact:        linux-pm@vger.kernel.org
505 Description:
506                 Represents the charging behaviour.
508                 Access: Read, Write
510                 Valid values:
511                         ================ ====================================
512                         auto:            Charge normally, respect thresholds
513                         inhibit-charge:  Do not charge while AC is attached
514                         force-discharge: Force discharge while AC is attached
515                         ================ ====================================
517 What:           /sys/class/power_supply/<supply_name>/technology
518 Date:           May 2007
519 Contact:        linux-pm@vger.kernel.org
520 Description:
521                 Describes the battery technology supported by the supply.
523                 Access: Read
525                 Valid values:
526                               "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
527                               "NiCd", "LiMn"
530 What:           /sys/class/power_supply/<supply_name>/voltage_avg,
531 Date:           May 2007
532 Contact:        linux-pm@vger.kernel.org
533 Description:
534                 Reports an average VBAT voltage reading for the battery, over a
535                 fixed period. Normally devices will provide a fixed interval in
536                 which they average readings to smooth out the reported value.
538                 Access: Read
540                 Valid values: Represented in microvolts
542 What:           /sys/class/power_supply/<supply_name>/cycle_count
543 Date:           January 2010
544 Contact:        linux-pm@vger.kernel.org
545 Description:
546                 Reports the number of full charge + discharge cycles the
547                 battery has undergone.
549                 Access: Read
551                 Valid values:
552                         Integer > 0: representing full cycles
553                         Integer = 0: cycle_count info is not available
555 **USB Properties**
557 What:           /sys/class/power_supply/<supply_name>/input_current_limit
558 Date:           July 2014
559 Contact:        linux-pm@vger.kernel.org
560 Description:
561                 Details the incoming IBUS current limit currently set in the
562                 supply. Normally this is configured based on the type of
563                 connection made (e.g. A configured SDP should output a maximum
564                 of 500mA so the input current limit is set to the same value).
565                 Use preferably input_power_limit, and for problems that can be
566                 solved using power limit use input_current_limit.
568                 Access: Read, Write
570                 Valid values: Represented in microamps
572 What:           /sys/class/power_supply/<supply_name>/input_voltage_limit
573 Date:           May 2019
574 Contact:        linux-pm@vger.kernel.org
575 Description:
576                 This entry configures the incoming VBUS voltage limit currently
577                 set in the supply. Normally this is configured based on
578                 system-level knowledge or user input (e.g. This is part of the
579                 Pixel C's thermal management strategy to effectively limit the
580                 input power to 5V when the screen is on to meet Google's skin
581                 temperature targets). Note that this feature should not be
582                 used for safety critical things.
583                 Use preferably input_power_limit, and for problems that can be
584                 solved using power limit use input_voltage_limit.
586                 Access: Read, Write
588                 Valid values: Represented in microvolts
590 What:           /sys/class/power_supply/<supply_name>/input_power_limit
591 Date:           May 2019
592 Contact:        linux-pm@vger.kernel.org
593 Description:
594                 This entry configures the incoming power limit currently set
595                 in the supply. Normally this is configured based on
596                 system-level knowledge or user input. Use preferably this
597                 feature to limit the incoming power and use current/voltage
598                 limit only for problems that can be solved using power limit.
600                 Access: Read, Write
602                 Valid values: Represented in microwatts
604 What:           /sys/class/power_supply/<supply_name>/online,
605 Date:           May 2007
606 Contact:        linux-pm@vger.kernel.org
607 Description:
608                 Indicates if VBUS is present for the supply. When the supply is
609                 online, and the supply allows it, then it's possible to switch
610                 between online states (e.g. Fixed -> Programmable for a PD_PPS
611                 USB supply so voltage and current can be controlled).
613                 Access: Read, Write
615                 Valid values:
617                         == ==================================================
618                         0: Offline
619                         1: Online Fixed - Fixed Voltage Supply
620                         2: Online Programmable - Programmable Voltage Supply
621                         == ==================================================
623 What:           /sys/class/power_supply/<supply_name>/usb_type
624 Date:           March 2018
625 Contact:        linux-pm@vger.kernel.org
626 Description:
627                 Reports what type of USB connection is currently active for
628                 the supply, for example it can show if USB-PD capable source
629                 is attached.
631                 Access: For power-supplies which consume USB power such
632                 as battery charger chips, this indicates the type of
633                 the connected USB power source and is Read-Only.
635                 For power-supplies which act as a USB power-source such as
636                 e.g. the UCS1002 USB Port Power Controller this is writable.
638                 Valid values:
639                               "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
640                               "PD_DRP", "PD_PPS", "BrickID"
642 **Device Specific Properties**
644 What:           /sys/class/power/ds2760-battery.*/charge_now
645 Date:           May 2010
646 KernelVersion:  2.6.35
647 Contact:        Daniel Mack <daniel@caiaq.de>
648 Description:
649                 This file is writeable and can be used to set the current
650                 coloumb counter value inside the battery monitor chip. This
651                 is needed for unavoidable corrections of aging batteries.
652                 A userspace daemon can monitor the battery charging logic
653                 and once the counter drops out of considerable bounds, take
654                 appropriate action.
656 What:           /sys/class/power/ds2760-battery.*/charge_full
657 Date:           May 2010
658 KernelVersion:  2.6.35
659 Contact:        Daniel Mack <daniel@caiaq.de>
660 Description:
661                 This file is writeable and can be used to set the assumed
662                 battery 'full level'. As batteries age, this value has to be
663                 amended over time.
665 What:           /sys/class/power_supply/max14577-charger/device/fast_charge_timer
666 Date:           October 2014
667 KernelVersion:  3.18.0
668 Contact:        Krzysztof Kozlowski <krzk@kernel.org>
669 Description:
670                 This entry shows and sets the maximum time the max14577
671                 charger operates in fast-charge mode. When the timer expires
672                 the device will terminate fast-charge mode (charging current
673                 will drop to 0 A) and will trigger interrupt.
675                 Valid values:
677                 - 5, 6 or 7 (hours),
678                 - 0: disabled.
680 What:           /sys/class/power_supply/max77693-charger/device/fast_charge_timer
681 Date:           January 2015
682 KernelVersion:  3.19.0
683 Contact:        Krzysztof Kozlowski <krzk@kernel.org>
684 Description:
685                 This entry shows and sets the maximum time the max77693
686                 charger operates in fast-charge mode. When the timer expires
687                 the device will terminate fast-charge mode (charging current
688                 will drop to 0 A) and will trigger interrupt.
690                 Valid values:
692                 - 4 - 16 (hours), step by 2 (rounded down)
693                 - 0: disabled.
695 What:           /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
696 Date:           January 2015
697 KernelVersion:  3.19.0
698 Contact:        Krzysztof Kozlowski <krzk@kernel.org>
699 Description:
700                 This entry shows and sets the charging current threshold for
701                 entering top-off charging mode. When charging current in fast
702                 charge mode drops below this value, the charger will trigger
703                 interrupt and start top-off charging mode.
705                 Valid values:
707                 - 100000 - 200000 (microamps), step by 25000 (rounded down)
708                 - 200000 - 350000 (microamps), step by 50000 (rounded down)
709                 - 0: disabled.
711 What:           /sys/class/power_supply/max77693-charger/device/top_off_timer
712 Date:           January 2015
713 KernelVersion:  3.19.0
714 Contact:        Krzysztof Kozlowski <krzk@kernel.org>
715 Description:
716                 This entry shows and sets the maximum time the max77693
717                 charger operates in top-off charge mode. When the timer expires
718                 the device will terminate top-off charge mode (charging current
719                 will drop to 0 A) and will trigger interrupt.
721                 Valid values:
723                 - 0 - 70 (minutes), step by 10 (rounded down)
725 What:           /sys/class/power_supply/bq24257-charger/ovp_voltage
726 Date:           October 2015
727 KernelVersion:  4.4.0
728 Contact:        Andreas Dannenberg <dannenberg@ti.com>
729 Description:
730                 This entry configures the overvoltage protection feature of bq24257-
731                 type charger devices. This feature protects the device and other
732                 components against damage from overvoltage on the input supply. See
733                 device datasheet for details.
735                 Valid values:
737                 - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
738                   10500000 (all uV)
740 What:           /sys/class/power_supply/bq24257-charger/in_dpm_voltage
741 Date:           October 2015
742 KernelVersion:  4.4.0
743 Contact:        Andreas Dannenberg <dannenberg@ti.com>
744 Description:
745                 This entry configures the input dynamic power path management voltage of
746                 bq24257-type charger devices. Once the supply drops to the configured
747                 voltage, the input current limit is reduced down to prevent the further
748                 drop of the supply. When the IC enters this mode, the charge current is
749                 lower than the set value. See device datasheet for details.
751                 Valid values:
753                 - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
754                   4760000 (all uV)
756 What:           /sys/class/power_supply/bq24257-charger/high_impedance_enable
757 Date:           October 2015
758 KernelVersion:  4.4.0
759 Contact:        Andreas Dannenberg <dannenberg@ti.com>
760 Description:
761                 This entry allows enabling the high-impedance mode of bq24257-type
762                 charger devices. If enabled, it places the charger IC into low power
763                 standby mode with the switch mode controller disabled. When disabled,
764                 the charger operates normally. See device datasheet for details.
766                 Valid values:
768                 - 1: enabled
769                 - 0: disabled
771 What:           /sys/class/power_supply/bq24257-charger/sysoff_enable
772 Date:           October 2015
773 KernelVersion:  4.4.0
774 Contact:        Andreas Dannenberg <dannenberg@ti.com>
775 Description:
776                 This entry allows enabling the sysoff mode of bq24257-type charger
777                 devices. If enabled and the input is removed, the internal battery FET
778                 is turned off in order to reduce the leakage from the BAT pin to less
779                 than 1uA. Note that on some devices/systems this disconnects the battery
780                 from the system. See device datasheet for details.
782                 Valid values:
784                 - 1: enabled
785                 - 0: disabled
787 What:           /sys/class/power_supply/<supply_name>/manufacture_year
788 Date:           January 2020
789 Contact:        linux-pm@vger.kernel.org
790 Description:
791                 Reports the year (following Gregorian calendar) when the device has been
792                 manufactured.
794                 Access: Read
796                 Valid values: Reported as integer
798 What:           /sys/class/power_supply/<supply_name>/manufacture_month
799 Date:           January 2020
800 Contact:        linux-pm@vger.kernel.org
801 Description:
802                 Reports the month when the device has been manufactured.
804                 Access: Read
806                 Valid values: 1-12
808 What:           /sys/class/power_supply/<supply_name>/manufacture_day
809 Date:           January 2020
810 Contact:        linux-pm@vger.kernel.org
811 Description:
812                 Reports the day of month when the device has been manufactured.
814                 Access: Read
815                 Valid values: 1-31
817 What:           /sys/class/power_supply/<supply_name>/extensions/<extension_name>
818 Date:           March 2025
819 Contact:        linux-pm@vger.kernel.org
820 Description:
821                 Reports the extensions registered to the power supply.
822                 Each entry is a link to the device which registered the extension.
824                 Access: Read