PM / Documentation: fix typos in power management description
Just two missing characters. Signed-off-by: Oskar Schirmer <oskar@scara.com> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
This commit is contained in:
parent
6887a4131d
commit
8d2c794108
1 changed files with 5 additions and 4 deletions
|
@ -583,9 +583,10 @@ for the given device during all power transitions, instead of the respective
|
||||||
subsystem-level callbacks. Specifically, if a device's pm_domain pointer is
|
subsystem-level callbacks. Specifically, if a device's pm_domain pointer is
|
||||||
not NULL, the ->suspend() callback from the object pointed to by it will be
|
not NULL, the ->suspend() callback from the object pointed to by it will be
|
||||||
executed instead of its subsystem's (e.g. bus type's) ->suspend() callback and
|
executed instead of its subsystem's (e.g. bus type's) ->suspend() callback and
|
||||||
anlogously for all of the remaining callbacks. In other words, power management
|
analogously for all of the remaining callbacks. In other words, power
|
||||||
domain callbacks, if defined for the given device, always take precedence over
|
management domain callbacks, if defined for the given device, always take
|
||||||
the callbacks provided by the device's subsystem (e.g. bus type).
|
precedence over the callbacks provided by the device's subsystem (e.g. bus
|
||||||
|
type).
|
||||||
|
|
||||||
The support for device power management domains is only relevant to platforms
|
The support for device power management domains is only relevant to platforms
|
||||||
needing to use the same device driver power management callbacks in many
|
needing to use the same device driver power management callbacks in many
|
||||||
|
@ -598,7 +599,7 @@ it into account in any way.
|
||||||
Device Low Power (suspend) States
|
Device Low Power (suspend) States
|
||||||
---------------------------------
|
---------------------------------
|
||||||
Device low-power states aren't standard. One device might only handle
|
Device low-power states aren't standard. One device might only handle
|
||||||
"on" and "off, while another might support a dozen different versions of
|
"on" and "off", while another might support a dozen different versions of
|
||||||
"on" (how many engines are active?), plus a state that gets back to "on"
|
"on" (how many engines are active?), plus a state that gets back to "on"
|
||||||
faster than from a full "off".
|
faster than from a full "off".
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue