diff options
Diffstat (limited to 'Documentation/power')
-rw-r--r-- | Documentation/power/pci.txt | 2 | ||||
-rw-r--r-- | Documentation/power/swsusp.txt | 8 | ||||
-rw-r--r-- | Documentation/power/tricks.txt | 2 | ||||
-rw-r--r-- | Documentation/power/userland-swsusp.txt | 2 | ||||
-rw-r--r-- | Documentation/power/video.txt | 2 |
5 files changed, 8 insertions, 8 deletions
diff --git a/Documentation/power/pci.txt b/Documentation/power/pci.txt index 73fc87e5dc3..24edf25b3bb 100644 --- a/Documentation/power/pci.txt +++ b/Documentation/power/pci.txt @@ -326,7 +326,7 @@ A reference implementation This is a typical implementation. Drivers can slightly change the order of the operations in the implementation, ignore some operations or add -more deriver specific operations in it, but drivers should do something like +more driver specific operations in it, but drivers should do something like this on the whole. 5. Resources diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt index 823b2cf6e3d..9ea2208b43b 100644 --- a/Documentation/power/swsusp.txt +++ b/Documentation/power/swsusp.txt @@ -156,7 +156,7 @@ instead set the PF_NOFREEZE process flag when creating the thread (and be very carefull). -Q: What is the difference between between "platform", "shutdown" and +Q: What is the difference between "platform", "shutdown" and "firmware" in /sys/power/disk? A: @@ -175,8 +175,8 @@ reliable. Q: I do not understand why you have such strong objections to idea of selective suspend. -A: Do selective suspend during runtime power managment, that's okay. But -its useless for suspend-to-disk. (And I do not see how you could use +A: Do selective suspend during runtime power management, that's okay. But +it's useless for suspend-to-disk. (And I do not see how you could use it for suspend-to-ram, I hope you do not want that). Lets see, so you suggest to @@ -211,7 +211,7 @@ slowness may not matter to you. It can always be fixed later. For devices like disk it does matter, you do not want to spindown for FREEZE. -Q: After resuming, system is paging heavilly, leading to very bad interactivity. +Q: After resuming, system is paging heavily, leading to very bad interactivity. A: Try running diff --git a/Documentation/power/tricks.txt b/Documentation/power/tricks.txt index c6d58d3da13..3b26bb502a4 100644 --- a/Documentation/power/tricks.txt +++ b/Documentation/power/tricks.txt @@ -9,7 +9,7 @@ If you want to trick swsusp/S3 into working, you might want to try: * turn off APIC and preempt -* use ext2. At least it has working fsck. [If something seemes to go +* use ext2. At least it has working fsck. [If something seems to go wrong, force fsck when you have a chance] * turn off modules diff --git a/Documentation/power/userland-swsusp.txt b/Documentation/power/userland-swsusp.txt index 94058220aaf..64755e9285d 100644 --- a/Documentation/power/userland-swsusp.txt +++ b/Documentation/power/userland-swsusp.txt @@ -91,7 +91,7 @@ unfreeze user space processes frozen by SNAPSHOT_UNFREEZE if they are still frozen when the device is being closed). Currently it is assumed that the userland utilities reading/writing the -snapshot image from/to the kernel will use a swap parition, called the resume +snapshot image from/to the kernel will use a swap partition, called the resume partition, as storage space. However, this is not really required, as they can use, for example, a special (blank) suspend partition or a file on a partition that is unmounted before SNAPSHOT_ATOMIC_SNAPSHOT and mounted afterwards. diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt index d859faa3a46..2b358498d09 100644 --- a/Documentation/power/video.txt +++ b/Documentation/power/video.txt @@ -16,7 +16,7 @@ problem for S1 standby, because hardware should retain its state over that. We either have to run video BIOS during early resume, or interpret it -using vbetool later, or maybe nothing is neccessary on particular +using vbetool later, or maybe nothing is necessary on particular system because video state is preserved. Unfortunately different methods work on different systems, and no known method suits all of them. |