add boot partition size

hc

2023-12-11 d2ccde1c8e90d38cee87a1b0309ad2827f3fd30d

 kernel/Documentation/ABI/testing/sysfs-power
..
..
@@ -47,14 +47,18 @@
47
47
 		suspend-to-disk mechanism.  Reading from this file returns
48
48
 		the name of the method by which the system will be put to
49
49
 		sleep on the next suspend.  There are four methods supported:
50
+
50
51
 		'firmware' - means that the memory image will be saved to disk
51
52
 		by some firmware, in which case we also assume that the
52
53
 		firmware will handle the system suspend.
54
+
53
55
 		'platform' - the memory image will be saved by the kernel and
54
56
 		the system will be put to sleep by the platform driver (e.g.
55
57
 		ACPI or other PM registers).
58
+
56
59
 		'shutdown' - the memory image will be saved by the kernel and
57
60
 		the system will be powered off.
61
+
58
62
 		'reboot' - the memory image will be saved by the kernel and
59
63
 		the system will be rebooted.
60
64
 
..
..
@@ -74,12 +78,12 @@
74
78
 		The suspend-to-disk method may be chosen by writing to this
75
79
 		file one of the accepted strings:
76
80
 
77
-		'firmware'
78
-		'platform'
79
-		'shutdown'
80
-		'reboot'
81
-		'testproc'
82
-		'test'
81
+		- 'firmware'
82
+		- 'platform'
83
+		- 'shutdown'
84
+		- 'reboot'
85
+		- 'testproc'
86
+		- 'test'
83
87
 
84
88
 		It will only change to 'firmware' or 'platform' if the system
85
89
 		supports that.
..
..
@@ -99,7 +103,7 @@
99
103
 		this file, the suspend image will be as small as possible.
100
104
 
101
105
 		Reading from this file will display the current image size
102
-		limit, which is set to 500 MB by default.
106
+		limit, which is set to around 2/5 of available RAM by default.
103
107
 
104
108
 What:		/sys/power/pm_trace
105
109
 Date:		August 2006
..
..
@@ -114,9 +118,9 @@
114
118
 		string representing a nonzero integer into it.
115
119
 
116
120
 		To use this debugging feature you should attempt to suspend
117
-		the machine, then reboot it and run
121
+		the machine, then reboot it and run::
118
122
 
119
-		dmesg -s 1000000 | grep 'hash matches'
123
+		  dmesg -s 1000000 | grep 'hash matches'
120
124
 
121
125
 		If you do not get any matches (or they appear to be false
122
126
 		positives), it is possible that the last PM event point
..
..
@@ -244,6 +248,7 @@
244
248
 		wakeup sources created with the help of /sys/power/wake_lock.
245
249
 		When a string is written to /sys/power/wake_unlock, it will be
246
250
 		assumed to represent the name of a wakeup source to deactivate.
251
+
247
252
 		If a wakeup source object of that name exists and is active at
248
253
 		the moment, it will be deactivated.
249
254
 
..
..
@@ -407,3 +412,16 @@
407
412
 Description:
408
413
 		The /sys/power/suspend_stats/last_failed_step file contains
409
414
 		the last failed step in the suspend/resume path.
415
+
416
+What:		/sys/power/sync_on_suspend
417
+Date:		October 2019
418
+Contact:	Jonas Meurer <jonas@freesources.org>
419
+Description:
420
+		This file controls whether or not the kernel will sync()
421
+		filesystems during system suspend (after freezing user space
422
+		and before suspending devices).
423
+
424
+		Writing a "1" to this file enables the sync() and writing a "0"
425
+		disables it.  Reads from the file return the current value.
426
+		The default is "1" if the build-time "SUSPEND_SKIP_SYNC" config
427
+		flag is unset, or "0" otherwise.