~hc/RK356X_SDK_RELEASE.git

..	..	@@ -1,4 +1,4 @@
1		-===== General Properties =====
	1	+General Properties
2	2
3	3	What: /sys/class/power_supply/<supply_name>/manufacturer
4	4	Date: May 2007
..	..	@@ -34,16 +34,240 @@
34	34	Describes the main type of the supply.
35	35
36	36	Access: Read
37		- Valid values: "Battery", "UPS", "Mains", "USB"
	37	+ Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"
38	38
39		-===== Battery Properties =====
	39	+Battery and USB properties
	40	+
	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:
	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	+
	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:
	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	+
	79	+What: /sys/class/power_supply/<supply_name>/current_now
	80	+Date: May 2007
	81	+Contact: linux-pm@vger.kernel.org
	82	+Description:
	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	+
	104	+What: /sys/class/power_supply/<supply_name>/temp
	105	+Date: May 2007
	106	+Contact: linux-pm@vger.kernel.org
	107	+Description:
	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	+
	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:
	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	+
	146	+What: /sys/class/power_supply/<supply_name>/temp_alert_min
	147	+Date: July 2012
	148	+Contact: linux-pm@vger.kernel.org
	149	+Description:
	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	+
	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:
	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	+
	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:
	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	+
	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:
	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	+
	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:
	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	+
	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:
	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
40	262
41	263	What: /sys/class/power_supply/<supply_name>/capacity
42	264	Date: May 2007
43	265	Contact: linux-pm@vger.kernel.org
44	266	Description:
45	267	Fine grain representation of battery capacity.
	268	+
46	269	Access: Read
	270	+
47	271	Valid values: 0 - 100 (percent)
48	272
49	273	What: /sys/class/power_supply/<supply_name>/capacity_alert_max
..	..	@@ -58,6 +282,7 @@
58	282	low).
59	283
60	284	Access: Read, Write
	285	+
61	286	Valid values: 0 - 100 (percent)
62	287
63	288	What: /sys/class/power_supply/<supply_name>/capacity_alert_min
..	..	@@ -72,6 +297,23 @@
72	297	critically low).
73	298
74	299	Access: Read, Write
	300	+
	301	+ Valid values: 0 - 100 (percent)
	302	+
	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.
	314	+
	315	+ Access: Read
	316	+
75	317	Valid values: 0 - 100 (percent)
76	318
77	319	What: /sys/class/power_supply/<supply_name>/capacity_level
..	..	@@ -81,48 +323,70 @@
81	323	Coarse representation of battery capacity.
82	324
83	325	Access: Read
84		- Valid values: "Unknown", "Critical", "Low", "Normal", "High",
	326	+
	327	+ Valid values:
	328	+ "Unknown", "Critical", "Low", "Normal", "High",
85	329	"Full"
86	330
87		-What: /sys/class/power_supply/<supply_name>/current_avg
88		-Date: May 2007
	331	+What: /sys/class/power_supply/<supply_name>/charge_control_limit
	332	+Date: Oct 2012
89	333	Contact: linux-pm@vger.kernel.org
90	334	Description:
91		- Reports an average IBAT current reading for the battery, over a
92		- fixed period. Normally devices will provide a fixed interval in
93		- which they average readings to smooth out the reported value.
	335	+ Maximum allowable charging current. Used for charge rate
	336	+ throttling for thermal cooling or improving battery health.
94	337
95		- Access: Read
	338	+ Access: Read, Write
	339	+
96	340	Valid values: Represented in microamps
97	341
98		-What: /sys/class/power_supply/<supply_name>/current_max
99		-Date: October 2010
	342	+What: /sys/class/power_supply/<supply_name>/charge_control_limit_max
	343	+Date: Oct 2012
100	344	Contact: linux-pm@vger.kernel.org
101	345	Description:
102		- Reports the maximum IBAT current allowed into the battery.
	346	+ Maximum legal value for the charge_control_limit property.
103	347
104	348	Access: Read
	349	+
105	350	Valid values: Represented in microamps
106	351
107		-What: /sys/class/power_supply/<supply_name>/current_now
108		-Date: May 2007
	352	+What: /sys/class/power_supply/<supply_name>/charge_control_start_threshold
	353	+Date: April 2019
109	354	Contact: linux-pm@vger.kernel.org
110	355	Description:
111		- Reports an instant, single IBAT current reading for the battery.
112		- This value is not averaged/smoothed.
	356	+ Represents a battery percentage level, below which charging will
	357	+ begin.
113	358
114		- Access: Read
115		- Valid values: Represented in microamps
	359	+ Access: Read, Write
	360	+ Valid values: 0 - 100 (percent)
	361	+
	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.
	368	+
	369	+ Access: Read, Write
	370	+
	371	+ Valid values: 0 - 100 (percent)
116	372
117	373	What: /sys/class/power_supply/<supply_name>/charge_type
118	374	Date: July 2009
119	375	Contact: linux-pm@vger.kernel.org
120	376	Description:
121	377	Represents the type of charging currently being applied to the
122		- battery.
	378	+ battery. "Trickle", "Fast", and "Standard" all mean different
	379	+ charging speeds. "Adaptive" means that the charger uses some
	380	+ algorithm to adjust the charge rate dynamically, without
	381	+ any user configuration required. "Custom" means that the charger
	382	+ uses the charge_control_* properties as configuration for some
	383	+ different algorithm.
123	384
124		- Access: Read
125		- Valid values: "Unknown", "N/A", "Trickle", "Fast"
	385	+ Access: Read, Write
	386	+
	387	+ Valid values:
	388	+ "Unknown", "N/A", "Trickle", "Fast", "Standard",
	389	+ "Adaptive", "Custom"
126	390
127	391	What: /sys/class/power_supply/<supply_name>/charge_term_current
128	392	Date: July 2014
..	..	@@ -132,6 +396,7 @@
132	396	when the battery is considered full and charging should end.
133	397
134	398	Access: Read
	399	+
135	400	Valid values: Represented in microamps
136	401
137	402	What: /sys/class/power_supply/<supply_name>/health
..	..	@@ -142,10 +407,13 @@
142	407	functionality.
143	408
144	409	Access: Read
145		- Valid values: "Unknown", "Good", "Overheat", "Dead",
	410	+
	411	+ Valid values:
	412	+ "Unknown", "Good", "Overheat", "Dead",
146	413	"Over voltage", "Unspecified failure", "Cold",
147	414	"Watchdog timer expire", "Safety timer expire",
148		- "Over current", "Warm", "Cool", "Hot"
	415	+ "Over current", "Calibration required", "Warm",
	416	+ "Cool", "Hot"
149	417
150	418	What: /sys/class/power_supply/<supply_name>/precharge_current
151	419	Date: June 2017
..	..	@@ -155,6 +423,7 @@
155	423	for a battery charge cycle.
156	424
157	425	Access: Read
	426	+
158	427	Valid values: Represented in microamps
159	428
160	429	What: /sys/class/power_supply/<supply_name>/present
..	..	@@ -164,9 +433,13 @@
164	433	Reports whether a battery is present or not in the system.
165	434
166	435	Access: Read
	436	+
167	437	Valid values:
	438	+
	439	+ == =======
168	440	0: Absent
169	441	1: Present
	442	+ == =======
170	443
171	444	What: /sys/class/power_supply/<supply_name>/status
172	445	Date: May 2007
..	..	@@ -177,7 +450,9 @@
177	450	used to enable/disable charging to the battery.
178	451
179	452	Access: Read, Write
180		- Valid values: "Unknown", "Charging", "Discharging",
	453	+
	454	+ Valid values:
	455	+ "Unknown", "Charging", "Discharging",
181	456	"Not charging", "Full"
182	457
183	458	What: /sys/class/power_supply/<supply_name>/technology
..	..	@@ -187,66 +462,11 @@
187	462	Describes the battery technology supported by the supply.
188	463
189	464	Access: Read
190		- Valid values: "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
	465	+
	466	+ Valid values:
	467	+ "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
191	468	"NiCd", "LiMn"
192	469
193		-What: /sys/class/power_supply/<supply_name>/temp
194		-Date: May 2007
195		-Contact: linux-pm@vger.kernel.org
196		-Description:
197		- Reports the current TBAT battery temperature reading.
198		-
199		- Access: Read
200		- Valid values: Represented in 1/10 Degrees Celsius
201		-
202		-What: /sys/class/power_supply/<supply_name>/temp_alert_max
203		-Date: July 2012
204		-Contact: linux-pm@vger.kernel.org
205		-Description:
206		- Maximum TBAT temperature trip-wire value where the supply will
207		- notify user-space of the event. This is normally used for the
208		- battery charging scenario where user-space needs to know the
209		- battery temperature has crossed an upper threshold so it can
210		- take appropriate action (e.g. warning user that battery level is
211		- critically high, and charging has stopped).
212		-
213		- Access: Read
214		- Valid values: Represented in 1/10 Degrees Celsius
215		-
216		-What: /sys/class/power_supply/<supply_name>/temp_alert_min
217		-Date: July 2012
218		-Contact: linux-pm@vger.kernel.org
219		-Description:
220		- Minimum TBAT temperature trip-wire value where the supply will
221		- notify user-space of the event. This is normally used for the
222		- battery charging scenario where user-space needs to know the
223		- battery temperature has crossed a lower threshold so it can take
224		- appropriate action (e.g. warning user that battery level is
225		- high, and charging current has been reduced accordingly to
226		- remedy the situation).
227		-
228		- Access: Read
229		- Valid values: Represented in 1/10 Degrees Celsius
230		-
231		-What: /sys/class/power_supply/<supply_name>/temp_max
232		-Date: July 2014
233		-Contact: linux-pm@vger.kernel.org
234		-Description:
235		- Reports the maximum allowed TBAT battery temperature for
236		- charging.
237		-
238		- Access: Read
239		- Valid values: Represented in 1/10 Degrees Celsius
240		-
241		-What: /sys/class/power_supply/<supply_name>/temp_min
242		-Date: July 2014
243		-Contact: linux-pm@vger.kernel.org
244		-Description:
245		- Reports the minimum allowed TBAT battery temperature for
246		- charging.
247		-
248		- Access: Read
249		- Valid values: Represented in 1/10 Degrees Celsius
250	470
251	471	What: /sys/class/power_supply/<supply_name>/voltage_avg,
252	472	Date: May 2007
..	..	@@ -257,72 +477,10 @@
257	477	which they average readings to smooth out the reported value.
258	478
259	479	Access: Read
	480	+
260	481	Valid values: Represented in microvolts
261	482
262		-What: /sys/class/power_supply/<supply_name>/voltage_max,
263		-Date: January 2008
264		-Contact: linux-pm@vger.kernel.org
265		-Description:
266		- Reports the maximum safe VBAT voltage permitted for the battery,
267		- during charging.
268		-
269		- Access: Read
270		- Valid values: Represented in microvolts
271		-
272		-What: /sys/class/power_supply/<supply_name>/voltage_min,
273		-Date: January 2008
274		-Contact: linux-pm@vger.kernel.org
275		-Description:
276		- Reports the minimum safe VBAT voltage permitted for the battery,
277		- during discharging.
278		-
279		- Access: Read
280		- Valid values: Represented in microvolts
281		-
282		-What: /sys/class/power_supply/<supply_name>/voltage_now,
283		-Date: May 2007
284		-Contact: linux-pm@vger.kernel.org
285		-Description:
286		- Reports an instant, single VBAT voltage reading for the battery.
287		- This value is not averaged/smoothed.
288		-
289		- Access: Read
290		- Valid values: Represented in microvolts
291		-
292		-===== USB Properties =====
293		-
294		-What: /sys/class/power_supply/<supply_name>/current_avg
295		-Date: May 2007
296		-Contact: linux-pm@vger.kernel.org
297		-Description:
298		- Reports an average IBUS current reading over a fixed period.
299		- Normally devices will provide a fixed interval in which they
300		- average readings to smooth out the reported value.
301		-
302		- Access: Read
303		- Valid values: Represented in microamps
304		-
305		-
306		-What: /sys/class/power_supply/<supply_name>/current_max
307		-Date: October 2010
308		-Contact: linux-pm@vger.kernel.org
309		-Description:
310		- Reports the maximum IBUS current the supply can support.
311		-
312		- Access: Read
313		- Valid values: Represented in microamps
314		-
315		-What: /sys/class/power_supply/<supply_name>/current_now
316		-Date: May 2007
317		-Contact: linux-pm@vger.kernel.org
318		-Description:
319		- Reports the IBUS current supplied now. This value is generally
320		- read-only reporting, unless the 'online' state of the supply
321		- is set to be programmable, in which case this value can be set
322		- within the reported min/max range.
323		-
324		- Access: Read, Write
325		- Valid values: Represented in microamps
	483	+USB Properties
326	484
327	485	What: /sys/class/power_supply/<supply_name>/input_current_limit
328	486	Date: July 2014
..	..	@@ -332,9 +490,44 @@
332	490	supply. Normally this is configured based on the type of
333	491	connection made (e.g. A configured SDP should output a maximum
334	492	of 500mA so the input current limit is set to the same value).
	493	+ Use preferably input_power_limit, and for problems that can be
	494	+ solved using power limit use input_current_limit.
335	495
336	496	Access: Read, Write
	497	+
337	498	Valid values: Represented in microamps
	499	+
	500	+What: /sys/class/power_supply/<supply_name>/input_voltage_limit
	501	+Date: May 2019
	502	+Contact: linux-pm@vger.kernel.org
	503	+Description:
	504	+ This entry configures the incoming VBUS voltage limit currently
	505	+ set in the supply. Normally this is configured based on
	506	+ system-level knowledge or user input (e.g. This is part of the
	507	+ Pixel C's thermal management strategy to effectively limit the
	508	+ input power to 5V when the screen is on to meet Google's skin
	509	+ temperature targets). Note that this feature should not be
	510	+ used for safety critical things.
	511	+ Use preferably input_power_limit, and for problems that can be
	512	+ solved using power limit use input_voltage_limit.
	513	+
	514	+ Access: Read, Write
	515	+
	516	+ Valid values: Represented in microvolts
	517	+
	518	+What: /sys/class/power_supply/<supply_name>/input_power_limit
	519	+Date: May 2019
	520	+Contact: linux-pm@vger.kernel.org
	521	+Description:
	522	+ This entry configures the incoming power limit currently set
	523	+ in the supply. Normally this is configured based on
	524	+ system-level knowledge or user input. Use preferably this
	525	+ feature to limit the incoming power and use current/voltage
	526	+ limit only for problems that can be solved using power limit.
	527	+
	528	+ Access: Read, Write
	529	+
	530	+ Valid values: Represented in microwatts
338	531
339	532	What: /sys/class/power_supply/<supply_name>/online,
340	533	Date: May 2007
..	..	@@ -346,69 +539,14 @@
346	539	USB supply so voltage and current can be controlled).
347	540
348	541	Access: Read, Write
	542	+
349	543	Valid values:
	544	+
	545	+ == ==================================================
350	546	0: Offline
351	547	1: Online Fixed - Fixed Voltage Supply
352	548	2: Online Programmable - Programmable Voltage Supply
353		-
354		-What: /sys/class/power_supply/<supply_name>/temp
355		-Date: May 2007
356		-Contact: linux-pm@vger.kernel.org
357		-Description:
358		- Reports the current supply temperature reading. This would
359		- normally be the internal temperature of the device itself (e.g
360		- TJUNC temperature of an IC)
361		-
362		- Access: Read
363		- Valid values: Represented in 1/10 Degrees Celsius
364		-
365		-What: /sys/class/power_supply/<supply_name>/temp_alert_max
366		-Date: July 2012
367		-Contact: linux-pm@vger.kernel.org
368		-Description:
369		- Maximum supply temperature trip-wire value where the supply will
370		- notify user-space of the event. This is normally used for the
371		- charging scenario where user-space needs to know the supply
372		- temperature has crossed an upper threshold so it can take
373		- appropriate action (e.g. warning user that the supply
374		- temperature is critically high, and charging has stopped to
375		- remedy the situation).
376		-
377		- Access: Read
378		- Valid values: Represented in 1/10 Degrees Celsius
379		-
380		-What: /sys/class/power_supply/<supply_name>/temp_alert_min
381		-Date: July 2012
382		-Contact: linux-pm@vger.kernel.org
383		-Description:
384		- Minimum supply temperature trip-wire value where the supply will
385		- notify user-space of the event. This is normally used for the
386		- charging scenario where user-space needs to know the supply
387		- temperature has crossed a lower threshold so it can take
388		- appropriate action (e.g. warning user that the supply
389		- temperature is high, and charging current has been reduced
390		- accordingly to remedy the situation).
391		-
392		- Access: Read
393		- Valid values: Represented in 1/10 Degrees Celsius
394		-
395		-What: /sys/class/power_supply/<supply_name>/temp_max
396		-Date: July 2014
397		-Contact: linux-pm@vger.kernel.org
398		-Description:
399		- Reports the maximum allowed supply temperature for operation.
400		-
401		- Access: Read
402		- Valid values: Represented in 1/10 Degrees Celsius
403		-
404		-What: /sys/class/power_supply/<supply_name>/temp_min
405		-Date: July 2014
406		-Contact: linux-pm@vger.kernel.org
407		-Description:
408		- Reports the mainimum allowed supply temperature for operation.
409		-
410		- Access: Read
411		- Valid values: Represented in 1/10 Degrees Celsius
	549	+ == ==================================================
412	550
413	551	What: /sys/class/power_supply/<supply_name>/usb_type
414	552	Date: March 2018
..	..	@@ -419,40 +557,12 @@
419	557	is attached.
420	558
421	559	Access: Read-Only
422		- Valid values: "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
	560	+
	561	+ Valid values:
	562	+ "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
423	563	"PD_DRP", "PD_PPS", "BrickID"
424	564
425		-What: /sys/class/power_supply/<supply_name>/voltage_max
426		-Date: January 2008
427		-Contact: linux-pm@vger.kernel.org
428		-Description:
429		- Reports the maximum VBUS voltage the supply can support.
430		-
431		- Access: Read
432		- Valid values: Represented in microvolts
433		-
434		-What: /sys/class/power_supply/<supply_name>/voltage_min
435		-Date: January 2008
436		-Contact: linux-pm@vger.kernel.org
437		-Description:
438		- Reports the minimum VBUS voltage the supply can support.
439		-
440		- Access: Read
441		- Valid values: Represented in microvolts
442		-
443		-What: /sys/class/power_supply/<supply_name>/voltage_now
444		-Date: May 2007
445		-Contact: linux-pm@vger.kernel.org
446		-Description:
447		- Reports the VBUS voltage supplied now. This value is generally
448		- read-only reporting, unless the 'online' state of the supply
449		- is set to be programmable, in which case this value can be set
450		- within the reported min/max range.
451		-
452		- Access: Read, Write
453		- Valid values: Represented in microvolts
454		-
455		-===== Device Specific Properties =====
	565	+Device Specific Properties
456	566
457	567	What: /sys/class/power/ds2760-battery.*/charge_now
458	568	Date: May 2010
..	..	@@ -486,6 +596,7 @@
486	596	will drop to 0 A) and will trigger interrupt.
487	597
488	598	Valid values:
	599	+
489	600	- 5, 6 or 7 (hours),
490	601	- 0: disabled.
491	602
..	..	@@ -500,6 +611,7 @@
500	611	will drop to 0 A) and will trigger interrupt.
501	612
502	613	Valid values:
	614	+
503	615	- 4 - 16 (hours), step by 2 (rounded down)
504	616	- 0: disabled.
505	617
..	..	@@ -514,6 +626,7 @@
514	626	interrupt and start top-off charging mode.
515	627
516	628	Valid values:
	629	+
517	630	- 100000 - 200000 (microamps), step by 25000 (rounded down)
518	631	- 200000 - 350000 (microamps), step by 50000 (rounded down)
519	632	- 0: disabled.
..	..	@@ -529,6 +642,7 @@
529	642	will drop to 0 A) and will trigger interrupt.
530	643
531	644	Valid values:
	645	+
532	646	- 0 - 70 (minutes), step by 10 (rounded down)
533	647
534	648	What: /sys/class/power_supply/bq24257-charger/ovp_voltage
..	..	@@ -542,6 +656,7 @@
542	656	device datasheet for details.
543	657
544	658	Valid values:
	659	+
545	660	- 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
546	661	10500000 (all uV)
547	662
..	..	@@ -557,6 +672,7 @@
557	672	lower than the set value. See device datasheet for details.
558	673
559	674	Valid values:
	675	+
560	676	- 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
561	677	4760000 (all uV)
562	678
..	..	@@ -571,6 +687,7 @@
571	687	the charger operates normally. See device datasheet for details.
572	688
573	689	Valid values:
	690	+
574	691	- 1: enabled
575	692	- 0: disabled
576	693
..	..	@@ -586,5 +703,36 @@
586	703	from the system. See device datasheet for details.
587	704
588	705	Valid values:
	706	+
589	707	- 1: enabled
590	708	- 0: disabled
	709	+
	710	+What: /sys/class/power_supply/<supply_name>/manufacture_year
	711	+Date: January 2020
	712	+Contact: linux-pm@vger.kernel.org
	713	+Description:
	714	+ Reports the year (following Gregorian calendar) when the device has been
	715	+ manufactured.
	716	+
	717	+ Access: Read
	718	+
	719	+ Valid values: Reported as integer
	720	+
	721	+What: /sys/class/power_supply/<supply_name>/manufacture_month
	722	+Date: January 2020
	723	+Contact: linux-pm@vger.kernel.org
	724	+Description:
	725	+ Reports the month when the device has been manufactured.
	726	+
	727	+ Access: Read
	728	+
	729	+ Valid values: 1-12
	730	+
	731	+What: /sys/class/power_supply/<supply_name>/manufacture_day
	732	+Date: January 2020
	733	+Contact: linux-pm@vger.kernel.org
	734	+Description:
	735	+ Reports the day of month when the device has been manufactured.
	736	+
	737	+ Access: Read
	738	+ Valid values: 1-31