sysfs-class-power 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773
  1. **General Properties**
  2. What: /sys/class/power_supply/<supply_name>/manufacturer
  3. Date: May 2007
  4. Contact: [email protected]
  5. Description:
  6. Reports the name of the device manufacturer.
  7. Access: Read
  8. Valid values: Represented as string
  9. What: /sys/class/power_supply/<supply_name>/model_name
  10. Date: May 2007
  11. Contact: [email protected]
  12. Description:
  13. Reports the name of the device model.
  14. Access: Read
  15. Valid values: Represented as string
  16. What: /sys/class/power_supply/<supply_name>/serial_number
  17. Date: January 2008
  18. Contact: [email protected]
  19. Description:
  20. Reports the serial number of the device.
  21. Access: Read
  22. Valid values: Represented as string
  23. What: /sys/class/power_supply/<supply_name>/type
  24. Date: May 2010
  25. Contact: [email protected]
  26. Description:
  27. Describes the main type of the supply.
  28. Access: Read
  29. Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"
  30. **Battery and USB properties**
  31. What: /sys/class/power_supply/<supply_name>/current_avg
  32. Date: May 2007
  33. Contact: [email protected]
  34. Description:
  35. Battery:
  36. Reports an average IBAT current reading for the battery, over
  37. a fixed period. Normally devices will provide a fixed interval
  38. in which they average readings to smooth out the reported
  39. value.
  40. USB:
  41. Reports an average IBUS current reading over a fixed period.
  42. Normally devices will provide a fixed interval in which they
  43. average readings to smooth out the reported value.
  44. Access: Read
  45. Valid values: Represented in microamps. Negative values are
  46. used for discharging batteries, positive values for charging
  47. batteries and for USB IBUS current.
  48. What: /sys/class/power_supply/<supply_name>/current_max
  49. Date: October 2010
  50. Contact: [email protected]
  51. Description:
  52. Battery:
  53. Reports the maximum IBAT current allowed into the battery.
  54. USB:
  55. Reports the maximum IBUS current the supply can support.
  56. Access: Read
  57. Valid values: Represented in microamps
  58. What: /sys/class/power_supply/<supply_name>/current_now
  59. Date: May 2007
  60. Contact: [email protected]
  61. Description:
  62. Battery:
  63. Reports an instant, single IBAT current reading for the
  64. battery. This value is not averaged/smoothed.
  65. Access: Read
  66. USB:
  67. Reports the IBUS current supplied now. This value is generally
  68. read-only reporting, unless the 'online' state of the supply
  69. is set to be programmable, in which case this value can be set
  70. within the reported min/max range.
  71. Access: Read, Write
  72. Valid values: Represented in microamps. Negative values are
  73. used for discharging batteries, positive values for charging
  74. batteries and for USB IBUS current.
  75. What: /sys/class/power_supply/<supply_name>/temp
  76. Date: May 2007
  77. Contact: [email protected]
  78. Description:
  79. Battery:
  80. Reports the current TBAT battery temperature reading.
  81. USB:
  82. Reports the current supply temperature reading. This would
  83. normally be the internal temperature of the device itself
  84. (e.g TJUNC temperature of an IC)
  85. Access: Read
  86. Valid values: Represented in 1/10 Degrees Celsius
  87. What: /sys/class/power_supply/<supply_name>/temp_alert_max
  88. Date: July 2012
  89. Contact: [email protected]
  90. Description:
  91. Battery:
  92. Maximum TBAT temperature trip-wire value where the supply will
  93. notify user-space of the event.
  94. USB:
  95. Maximum supply temperature trip-wire value where the supply
  96. will notify user-space of the event.
  97. This is normally used for the charging scenario where
  98. user-space needs to know if the temperature has crossed an
  99. upper threshold so it can take appropriate action (e.g. warning
  100. user that the temperature is critically high, and charging has
  101. stopped).
  102. Access: Read
  103. Valid values: Represented in 1/10 Degrees Celsius
  104. What: /sys/class/power_supply/<supply_name>/temp_alert_min
  105. Date: July 2012
  106. Contact: [email protected]
  107. Description:
  108. Battery:
  109. Minimum TBAT temperature trip-wire value where the supply will
  110. notify user-space of the event.
  111. USB:
  112. Minimum supply temperature trip-wire value where the supply
  113. will notify user-space of the event.
  114. This is normally used for the charging scenario where user-space
  115. needs to know if the temperature has crossed a lower threshold
  116. so it can take appropriate action (e.g. warning user that
  117. temperature level is high, and charging current has been
  118. reduced accordingly to remedy the situation).
  119. Access: Read
  120. Valid values: Represented in 1/10 Degrees Celsius
  121. What: /sys/class/power_supply/<supply_name>/temp_max
  122. Date: July 2014
  123. Contact: [email protected]
  124. Description:
  125. Battery:
  126. Reports the maximum allowed TBAT battery temperature for
  127. charging.
  128. USB:
  129. Reports the maximum allowed supply temperature for operation.
  130. Access: Read
  131. Valid values: Represented in 1/10 Degrees Celsius
  132. What: /sys/class/power_supply/<supply_name>/temp_min
  133. Date: July 2014
  134. Contact: [email protected]
  135. Description:
  136. Battery:
  137. Reports the minimum allowed TBAT battery temperature for
  138. charging.
  139. USB:
  140. Reports the minimum allowed supply temperature for operation.
  141. Access: Read
  142. Valid values: Represented in 1/10 Degrees Celsius
  143. What: /sys/class/power_supply/<supply_name>/voltage_max,
  144. Date: January 2008
  145. Contact: [email protected]
  146. Description:
  147. Battery:
  148. Reports the maximum safe VBAT voltage permitted for the
  149. battery, during charging.
  150. USB:
  151. Reports the maximum VBUS voltage the supply can support.
  152. Access: Read
  153. Valid values: Represented in microvolts
  154. What: /sys/class/power_supply/<supply_name>/voltage_min,
  155. Date: January 2008
  156. Contact: [email protected]
  157. Description:
  158. Battery:
  159. Reports the minimum safe VBAT voltage permitted for the
  160. battery, during discharging.
  161. USB:
  162. Reports the minimum VBUS voltage the supply can support.
  163. Access: Read
  164. Valid values: Represented in microvolts
  165. What: /sys/class/power_supply/<supply_name>/voltage_now,
  166. Date: May 2007
  167. Contact: [email protected]
  168. Description:
  169. Battery:
  170. Reports an instant, single VBAT voltage reading for the
  171. battery. This value is not averaged/smoothed.
  172. Access: Read
  173. USB:
  174. Reports the VBUS voltage supplied now. This value is generally
  175. read-only reporting, unless the 'online' state of the supply
  176. is set to be programmable, in which case this value can be set
  177. within the reported min/max range.
  178. Access: Read, Write
  179. Valid values: Represented in microvolts
  180. **Battery Properties**
  181. What: /sys/class/power_supply/<supply_name>/capacity
  182. Date: May 2007
  183. Contact: [email protected]
  184. Description:
  185. Fine grain representation of battery capacity.
  186. Access: Read
  187. Valid values: 0 - 100 (percent)
  188. What: /sys/class/power_supply/<supply_name>/capacity_alert_max
  189. Date: July 2012
  190. Contact: [email protected]
  191. Description:
  192. Maximum battery capacity trip-wire value where the supply will
  193. notify user-space of the event. This is normally used for the
  194. battery discharging scenario where user-space needs to know the
  195. battery has dropped to an upper level so it can take
  196. appropriate action (e.g. warning user that battery level is
  197. low).
  198. Access: Read, Write
  199. Valid values: 0 - 100 (percent)
  200. What: /sys/class/power_supply/<supply_name>/capacity_alert_min
  201. Date: July 2012
  202. Contact: [email protected]
  203. Description:
  204. Minimum battery capacity trip-wire value where the supply will
  205. notify user-space of the event. This is normally used for the
  206. battery discharging scenario where user-space needs to know the
  207. battery has dropped to a lower level so it can take
  208. appropriate action (e.g. warning user that battery level is
  209. critically low).
  210. Access: Read, Write
  211. Valid values: 0 - 100 (percent)
  212. What: /sys/class/power_supply/<supply_name>/capacity_error_margin
  213. Date: April 2019
  214. Contact: [email protected]
  215. Description:
  216. Battery capacity measurement becomes unreliable without
  217. recalibration. This values provides the maximum error
  218. margin expected to exist by the fuel gauge in percent.
  219. Values close to 0% will be returned after (re-)calibration
  220. has happened. Over time the error margin will increase.
  221. 100% means, that the capacity related values are basically
  222. completely useless.
  223. Access: Read
  224. Valid values: 0 - 100 (percent)
  225. What: /sys/class/power_supply/<supply_name>/capacity_level
  226. Date: June 2009
  227. Contact: [email protected]
  228. Description:
  229. Coarse representation of battery capacity.
  230. Access: Read
  231. Valid values:
  232. "Unknown", "Critical", "Low", "Normal", "High",
  233. "Full"
  234. What: /sys/class/power_supply/<supply_name>/charge_control_limit
  235. Date: Oct 2012
  236. Contact: [email protected]
  237. Description:
  238. Maximum allowable charging current. Used for charge rate
  239. throttling for thermal cooling or improving battery health.
  240. Access: Read, Write
  241. Valid values: Represented in microamps
  242. What: /sys/class/power_supply/<supply_name>/charge_control_limit_max
  243. Date: Oct 2012
  244. Contact: [email protected]
  245. Description:
  246. Maximum legal value for the charge_control_limit property.
  247. Access: Read
  248. Valid values: Represented in microamps
  249. What: /sys/class/power_supply/<supply_name>/charge_control_start_threshold
  250. Date: April 2019
  251. Contact: [email protected]
  252. Description:
  253. Represents a battery percentage level, below which charging will
  254. begin.
  255. Access: Read, Write
  256. Valid values: 0 - 100 (percent)
  257. What: /sys/class/power_supply/<supply_name>/charge_control_end_threshold
  258. Date: April 2019
  259. Contact: [email protected]
  260. Description:
  261. Represents a battery percentage level, above which charging will
  262. stop. Not all hardware is capable of setting this to an arbitrary
  263. percentage. Drivers will round written values to the nearest
  264. supported value. Reading back the value will show the actual
  265. threshold set by the driver.
  266. Access: Read, Write
  267. Valid values: 0 - 100 (percent)
  268. What: /sys/class/power_supply/<supply_name>/charge_type
  269. Date: July 2009
  270. Contact: [email protected]
  271. Description:
  272. Represents the type of charging currently being applied to the
  273. battery. "Trickle", "Fast", and "Standard" all mean different
  274. charging speeds. "Adaptive" means that the charger uses some
  275. algorithm to adjust the charge rate dynamically, without
  276. any user configuration required. "Custom" means that the charger
  277. uses the charge_control_* properties as configuration for some
  278. different algorithm. "Long Life" means the charger reduces its
  279. charging rate in order to prolong the battery health. "Bypass"
  280. means the charger bypasses the charging path around the
  281. integrated converter allowing for a "smart" wall adaptor to
  282. perform the power conversion externally.
  283. Access: Read, Write
  284. Valid values:
  285. "Unknown", "N/A", "Trickle", "Fast", "Standard",
  286. "Adaptive", "Custom", "Long Life", "Bypass"
  287. What: /sys/class/power_supply/<supply_name>/charge_term_current
  288. Date: July 2014
  289. Contact: [email protected]
  290. Description:
  291. Reports the charging current value which is used to determine
  292. when the battery is considered full and charging should end.
  293. Access: Read
  294. Valid values: Represented in microamps
  295. What: /sys/class/power_supply/<supply_name>/health
  296. Date: May 2007
  297. Contact: [email protected]
  298. Description:
  299. Reports the health of the battery or battery side of charger
  300. functionality.
  301. Access: Read
  302. Valid values:
  303. "Unknown", "Good", "Overheat", "Dead",
  304. "Over voltage", "Unspecified failure", "Cold",
  305. "Watchdog timer expire", "Safety timer expire",
  306. "Over current", "Calibration required", "Warm",
  307. "Cool", "Hot", "No battery"
  308. What: /sys/class/power_supply/<supply_name>/precharge_current
  309. Date: June 2017
  310. Contact: [email protected]
  311. Description:
  312. Reports the charging current applied during pre-charging phase
  313. for a battery charge cycle.
  314. Access: Read
  315. Valid values: Represented in microamps
  316. What: /sys/class/power_supply/<supply_name>/present
  317. Date: May 2007
  318. Contact: [email protected]
  319. Description:
  320. Reports whether a battery is present or not in the system.
  321. Access: Read
  322. Valid values:
  323. == =======
  324. 0: Absent
  325. 1: Present
  326. == =======
  327. What: /sys/class/power_supply/<supply_name>/status
  328. Date: May 2007
  329. Contact: [email protected]
  330. Description:
  331. Represents the charging status of the battery. Normally this
  332. is read-only reporting although for some supplies this can be
  333. used to enable/disable charging to the battery.
  334. Access: Read, Write
  335. Valid values:
  336. "Unknown", "Charging", "Discharging",
  337. "Not charging", "Full"
  338. What: /sys/class/power_supply/<supply_name>/charge_behaviour
  339. Date: November 2021
  340. Contact: [email protected]
  341. Description:
  342. Represents the charging behaviour.
  343. Access: Read, Write
  344. Valid values:
  345. ================ ====================================
  346. auto: Charge normally, respect thresholds
  347. inhibit-charge: Do not charge while AC is attached
  348. force-discharge: Force discharge while AC is attached
  349. ================ ====================================
  350. What: /sys/class/power_supply/<supply_name>/technology
  351. Date: May 2007
  352. Contact: [email protected]
  353. Description:
  354. Describes the battery technology supported by the supply.
  355. Access: Read
  356. Valid values:
  357. "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
  358. "NiCd", "LiMn"
  359. What: /sys/class/power_supply/<supply_name>/voltage_avg,
  360. Date: May 2007
  361. Contact: [email protected]
  362. Description:
  363. Reports an average VBAT voltage reading for the battery, over a
  364. fixed period. Normally devices will provide a fixed interval in
  365. which they average readings to smooth out the reported value.
  366. Access: Read
  367. Valid values: Represented in microvolts
  368. What: /sys/class/power_supply/<supply_name>/cycle_count
  369. Date: January 2010
  370. Contact: [email protected]
  371. Description:
  372. Reports the number of full charge + discharge cycles the
  373. battery has undergone.
  374. Access: Read
  375. Valid values:
  376. Integer > 0: representing full cycles
  377. Integer = 0: cycle_count info is not available
  378. **USB Properties**
  379. What: /sys/class/power_supply/<supply_name>/input_current_limit
  380. Date: July 2014
  381. Contact: [email protected]
  382. Description:
  383. Details the incoming IBUS current limit currently set in the
  384. supply. Normally this is configured based on the type of
  385. connection made (e.g. A configured SDP should output a maximum
  386. of 500mA so the input current limit is set to the same value).
  387. Use preferably input_power_limit, and for problems that can be
  388. solved using power limit use input_current_limit.
  389. Access: Read, Write
  390. Valid values: Represented in microamps
  391. What: /sys/class/power_supply/<supply_name>/input_voltage_limit
  392. Date: May 2019
  393. Contact: [email protected]
  394. Description:
  395. This entry configures the incoming VBUS voltage limit currently
  396. set in the supply. Normally this is configured based on
  397. system-level knowledge or user input (e.g. This is part of the
  398. Pixel C's thermal management strategy to effectively limit the
  399. input power to 5V when the screen is on to meet Google's skin
  400. temperature targets). Note that this feature should not be
  401. used for safety critical things.
  402. Use preferably input_power_limit, and for problems that can be
  403. solved using power limit use input_voltage_limit.
  404. Access: Read, Write
  405. Valid values: Represented in microvolts
  406. What: /sys/class/power_supply/<supply_name>/input_power_limit
  407. Date: May 2019
  408. Contact: [email protected]
  409. Description:
  410. This entry configures the incoming power limit currently set
  411. in the supply. Normally this is configured based on
  412. system-level knowledge or user input. Use preferably this
  413. feature to limit the incoming power and use current/voltage
  414. limit only for problems that can be solved using power limit.
  415. Access: Read, Write
  416. Valid values: Represented in microwatts
  417. What: /sys/class/power_supply/<supply_name>/online,
  418. Date: May 2007
  419. Contact: [email protected]
  420. Description:
  421. Indicates if VBUS is present for the supply. When the supply is
  422. online, and the supply allows it, then it's possible to switch
  423. between online states (e.g. Fixed -> Programmable for a PD_PPS
  424. USB supply so voltage and current can be controlled).
  425. Access: Read, Write
  426. Valid values:
  427. == ==================================================
  428. 0: Offline
  429. 1: Online Fixed - Fixed Voltage Supply
  430. 2: Online Programmable - Programmable Voltage Supply
  431. == ==================================================
  432. What: /sys/class/power_supply/<supply_name>/usb_type
  433. Date: March 2018
  434. Contact: [email protected]
  435. Description:
  436. Reports what type of USB connection is currently active for
  437. the supply, for example it can show if USB-PD capable source
  438. is attached.
  439. Access: Read-Only
  440. Valid values:
  441. "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
  442. "PD_DRP", "PD_PPS", "BrickID"
  443. **Device Specific Properties**
  444. What: /sys/class/power/ds2760-battery.*/charge_now
  445. Date: May 2010
  446. KernelVersion: 2.6.35
  447. Contact: Daniel Mack <[email protected]>
  448. Description:
  449. This file is writeable and can be used to set the current
  450. coloumb counter value inside the battery monitor chip. This
  451. is needed for unavoidable corrections of aging batteries.
  452. A userspace daemon can monitor the battery charging logic
  453. and once the counter drops out of considerable bounds, take
  454. appropriate action.
  455. What: /sys/class/power/ds2760-battery.*/charge_full
  456. Date: May 2010
  457. KernelVersion: 2.6.35
  458. Contact: Daniel Mack <[email protected]>
  459. Description:
  460. This file is writeable and can be used to set the assumed
  461. battery 'full level'. As batteries age, this value has to be
  462. amended over time.
  463. What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
  464. Date: October 2014
  465. KernelVersion: 3.18.0
  466. Contact: Krzysztof Kozlowski <[email protected]>
  467. Description:
  468. This entry shows and sets the maximum time the max14577
  469. charger operates in fast-charge mode. When the timer expires
  470. the device will terminate fast-charge mode (charging current
  471. will drop to 0 A) and will trigger interrupt.
  472. Valid values:
  473. - 5, 6 or 7 (hours),
  474. - 0: disabled.
  475. What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer
  476. Date: January 2015
  477. KernelVersion: 3.19.0
  478. Contact: Krzysztof Kozlowski <[email protected]>
  479. Description:
  480. This entry shows and sets the maximum time the max77693
  481. charger operates in fast-charge mode. When the timer expires
  482. the device will terminate fast-charge mode (charging current
  483. will drop to 0 A) and will trigger interrupt.
  484. Valid values:
  485. - 4 - 16 (hours), step by 2 (rounded down)
  486. - 0: disabled.
  487. What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
  488. Date: January 2015
  489. KernelVersion: 3.19.0
  490. Contact: Krzysztof Kozlowski <[email protected]>
  491. Description:
  492. This entry shows and sets the charging current threshold for
  493. entering top-off charging mode. When charging current in fast
  494. charge mode drops below this value, the charger will trigger
  495. interrupt and start top-off charging mode.
  496. Valid values:
  497. - 100000 - 200000 (microamps), step by 25000 (rounded down)
  498. - 200000 - 350000 (microamps), step by 50000 (rounded down)
  499. - 0: disabled.
  500. What: /sys/class/power_supply/max77693-charger/device/top_off_timer
  501. Date: January 2015
  502. KernelVersion: 3.19.0
  503. Contact: Krzysztof Kozlowski <[email protected]>
  504. Description:
  505. This entry shows and sets the maximum time the max77693
  506. charger operates in top-off charge mode. When the timer expires
  507. the device will terminate top-off charge mode (charging current
  508. will drop to 0 A) and will trigger interrupt.
  509. Valid values:
  510. - 0 - 70 (minutes), step by 10 (rounded down)
  511. What: /sys/class/power_supply/bq24257-charger/ovp_voltage
  512. Date: October 2015
  513. KernelVersion: 4.4.0
  514. Contact: Andreas Dannenberg <[email protected]>
  515. Description:
  516. This entry configures the overvoltage protection feature of bq24257-
  517. type charger devices. This feature protects the device and other
  518. components against damage from overvoltage on the input supply. See
  519. device datasheet for details.
  520. Valid values:
  521. - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
  522. 10500000 (all uV)
  523. What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage
  524. Date: October 2015
  525. KernelVersion: 4.4.0
  526. Contact: Andreas Dannenberg <[email protected]>
  527. Description:
  528. This entry configures the input dynamic power path management voltage of
  529. bq24257-type charger devices. Once the supply drops to the configured
  530. voltage, the input current limit is reduced down to prevent the further
  531. drop of the supply. When the IC enters this mode, the charge current is
  532. lower than the set value. See device datasheet for details.
  533. Valid values:
  534. - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
  535. 4760000 (all uV)
  536. What: /sys/class/power_supply/bq24257-charger/high_impedance_enable
  537. Date: October 2015
  538. KernelVersion: 4.4.0
  539. Contact: Andreas Dannenberg <[email protected]>
  540. Description:
  541. This entry allows enabling the high-impedance mode of bq24257-type
  542. charger devices. If enabled, it places the charger IC into low power
  543. standby mode with the switch mode controller disabled. When disabled,
  544. the charger operates normally. See device datasheet for details.
  545. Valid values:
  546. - 1: enabled
  547. - 0: disabled
  548. What: /sys/class/power_supply/bq24257-charger/sysoff_enable
  549. Date: October 2015
  550. KernelVersion: 4.4.0
  551. Contact: Andreas Dannenberg <[email protected]>
  552. Description:
  553. This entry allows enabling the sysoff mode of bq24257-type charger
  554. devices. If enabled and the input is removed, the internal battery FET
  555. is turned off in order to reduce the leakage from the BAT pin to less
  556. than 1uA. Note that on some devices/systems this disconnects the battery
  557. from the system. See device datasheet for details.
  558. Valid values:
  559. - 1: enabled
  560. - 0: disabled
  561. What: /sys/class/power_supply/<supply_name>/manufacture_year
  562. Date: January 2020
  563. Contact: [email protected]
  564. Description:
  565. Reports the year (following Gregorian calendar) when the device has been
  566. manufactured.
  567. Access: Read
  568. Valid values: Reported as integer
  569. What: /sys/class/power_supply/<supply_name>/manufacture_month
  570. Date: January 2020
  571. Contact: [email protected]
  572. Description:
  573. Reports the month when the device has been manufactured.
  574. Access: Read
  575. Valid values: 1-12
  576. What: /sys/class/power_supply/<supply_name>/manufacture_day
  577. Date: January 2020
  578. Contact: [email protected]
  579. Description:
  580. Reports the day of month when the device has been manufactured.
  581. Access: Read
  582. Valid values: 1-31