Source
16
16
resolve all suspend/resume-related problems in the test system before you start
17
17
testing the new driver. Please see Documentation/power/basic-pm-debugging.txt
18
18
for more information about the debugging of suspend/resume functionality.
19
19
20
20
2. Testing the driver
21
21
22
22
Once you have resolved the suspend/resume-related problems with your test system
23
23
without the new driver, you are ready to test it:
24
24
25
25
a) Build the driver as a module, load it and try the test modes of hibernation
26
-
(see: Documents/power/basic-pm-debugging.txt, 1).
26
+
(see: Documentation/power/basic-pm-debugging.txt, 1).
27
27
28
28
b) Load the driver and attempt to hibernate in the "reboot", "shutdown" and
29
-
"platform" modes (see: Documents/power/basic-pm-debugging.txt, 1).
29
+
"platform" modes (see: Documentation/power/basic-pm-debugging.txt, 1).
30
30
31
31
c) Compile the driver directly into the kernel and try the test modes of
32
32
hibernation.
33
33
34
34
d) Attempt to hibernate with the driver compiled directly into the kernel
35
35
in the "reboot", "shutdown" and "platform" modes.
36
36
37
-
e) Try the test modes of suspend (see: Documents/power/basic-pm-debugging.txt,
37
+
e) Try the test modes of suspend (see: Documentation/power/basic-pm-debugging.txt,
38
38
2). [As far as the STR tests are concerned, it should not matter whether or
39
39
not the driver is built as a module.]
40
40
41
41
f) Attempt to suspend to RAM using the s2ram tool with the driver loaded
42
-
(see: Documents/power/basic-pm-debugging.txt, 2).
42
+
(see: Documentation/power/basic-pm-debugging.txt, 2).
43
43
44
44
Each of the above tests should be repeated several times and the STD tests
45
45
should be mixed with the STR tests. If any of them fails, the driver cannot be
46
46
regarded as suspend/resume-safe.