luck/tmp_suning_uos_patched
1
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: power: Fix typo in Documentation/power

Browse Source 
This patch fix spelling typos found in Documentation/power.

Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Masanari Iida 2014-11-08 17:54:51 +09:00 committed by Jonathan Corbet
parent c0d7305cb3
commit 1f999d14fc
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/power/runtime_pm.txt
View File

@ -229,13 +229,13 @@ defined in include/linux/pm.h:
- if set, the value of child_count is ignored (but still updated) - if set, the value of child_count is ignored (but still updated)
unsigned int disable_depth; unsigned int disable_depth;
- used for disabling the helper funcions (they work normally if this is - used for disabling the helper functions (they work normally if this is
equal to zero); the initial value of it is 1 (i.e. runtime PM is equal to zero); the initial value of it is 1 (i.e. runtime PM is
initially disabled for all devices) initially disabled for all devices)
int runtime_error; int runtime_error;
- if set, there was a fatal error (one of the callbacks returned error code - if set, there was a fatal error (one of the callbacks returned error code
as described in Section 2), so the helper funtions will not work until as described in Section 2), so the helper functions will not work until
this flag is cleared; this is the error code returned by the failing this flag is cleared; this is the error code returned by the failing
callback callback
@ -524,7 +524,7 @@ pm_runtime_put_sync_autosuspend()
5. Runtime PM Initialization, Device Probing and Removal 5. Runtime PM Initialization, Device Probing and Removal
Initially, the runtime PM is disabled for all devices, which means that the Initially, the runtime PM is disabled for all devices, which means that the
majority of the runtime PM helper funtions described in Section 4 will return majority of the runtime PM helper functions described in Section 4 will return
-EAGAIN until pm_runtime_enable() is called for the device. -EAGAIN until pm_runtime_enable() is called for the device.
In addition to that, the initial runtime PM status of all devices is In addition to that, the initial runtime PM status of all devices is

2
Documentation/power/suspend-and-interrupts.txt
View File

@ -77,7 +77,7 @@ Calling enable_irq_wake() causes suspend_device_irqs() to treat the given IRQ
in a special way. Namely, the IRQ remains enabled, by on the first interrupt in a special way. Namely, the IRQ remains enabled, by on the first interrupt
it will be disabled, marked as pending and "suspended" so that it will be it will be disabled, marked as pending and "suspended" so that it will be
re-enabled by resume_device_irqs() during the subsequent system resume. Also re-enabled by resume_device_irqs() during the subsequent system resume. Also
the PM core is notified about the event which casues the system suspend in the PM core is notified about the event which causes the system suspend in
progress to be aborted (that doesn't have to happen immediately, but at one progress to be aborted (that doesn't have to happen immediately, but at one
of the points where the suspend thread looks for pending wakeup events). of the points where the suspend thread looks for pending wakeup events).

2
Documentation/power/userland-swsusp.txt
View File

@ -99,7 +99,7 @@ SNAPSHOT_S2RAM - suspend to RAM; using this call causes the kernel to
The device's read() operation can be used to transfer the snapshot image from The device's read() operation can be used to transfer the snapshot image from
the kernel. It has the following limitations: the kernel. It has the following limitations:
- you cannot read() more than one virtual memory page at a time - you cannot read() more than one virtual memory page at a time
- read()s across page boundaries are impossible (ie. if ypu read() 1/2 of - read()s across page boundaries are impossible (ie. if you read() 1/2 of
a page in the previous call, you will only be able to read() a page in the previous call, you will only be able to read()
_at_ _most_ 1/2 of the page in the next call) _at_ _most_ 1/2 of the page in the next call)