Documentation-power-states.txt

Chinese translated version of Documentation/power/states.txt


If you have any comment or update to the content, please contact the
original document maintainer directly.  However, if you have a problem
communicating in English you can also ask the Chinese maintainer for
help.  Contact the Chinese maintainer if this translation is outdated
or if there is a problem with the translation.


Maintainer: Eric W. Biederman <ebiederman@xmission.com>
Chinese maintainer: Shao Qi <shaoqitony@gmail.com>
---------------------------------------------------------------------
Documentation/power/states.txt 的中文翻译


如果想评论或更新本文的内容，请直接联系原文档的维护者。如果你使用英文
交流有困难的话，也可以向中文版维护者求助。如果本翻译更新不及时或者翻
译存在问题，请联系中文版维护者。
英文版维护者： Eric W. Biederman <ebiederman@xmission.com>
中文版维护者： 邵奇 Shao Qi <shaoqitony@gmail.com>
中文版翻译者： 邵奇 Shao Qi <shaoqitony@gmail.com>
中文版校译者： 邵奇 Shao Qi <shaoqitony@gmail.com>


以下为正文
---------------------------------------------------------------------


 
System Power Management States
系统电源管理状态




The kernel supports four power management states generically, though
one is generic and the other three are dependent on platform support
code to implement the low-level details for each state.
一般来说，内核支持4种电源管理状态，不过一个是通用型的，另外三个是依赖于
对实现每个状态的低级细节的平台支持代码。


This file describes each state, what they are
commonly called, what ACPI state they map to, and what string to write
to /sys/power/state to enter that state
此文件描述了每一个状态，它们一般被叫做什么，它们映射到什么ACPI状态，写入
什么到/sys/power/state已进入那个状态。


state:          Freeze / Low-Power Idle
ACPI state:     S0
String:         "freeze"


This state is a generic, pure software, light-weight, low-power state.
It allows more energy to be saved relative to idle by freezing user
space and putting all I/O devices into low-power states (possibly
lower-power than available at run time), such that the processors can
spend more time in their idle states.
此状态是通用的，纯软件的，轻量级的，低功耗状态。它通过空闲时冻结用户空间
，使所有I/O设备进入低功耗状态（可能比运行时更低功耗）以节省更多的功耗，
这样的话，在空闲状态时，处理器能获得更多时间。


This state can be used for platforms without Standby/Suspend-to-RAM
support, or it can be used in addition to Suspend-to-RAM (memory sleep)
to provide reduced resume latency.
此状态能用于平台无待机/挂起到内存支持，或者能用来减少除了挂起到内存（存储器
休眠）之外的恢复延迟。


State:          Standby / Power-On Suspend
ACPI State:     S1
String:         "standby"


This state offers minimal, though real, power savings, while providing
a very low-latency transition back to a working system. No operating
state is lost (the CPU retains power), so the system easily starts up
again where it left off. 
当提供非常低延迟的回到工作系统的转换，此状态提供真正的最低限度的节能。没有
操作状态会丢失（CPU一直通电）。所以，系统能很容易地从中断处再开始。


We try to put devices in a low-power state equivalent to D1, which
also offers low power savings, but low resume latency. Not all devices
support D1, and those that don't are left on. 
我们尝试使设备处于类似D1的低功耗状态，还使得节能和低恢复延迟并存。不是所有
设备都支持D1，并且不支持的谁呗都被抛弃了。




State:          Suspend-to-RAM
ACPI State:     S3
String:         "mem"


This state offers significant power savings as everything in the
system is put into a low-power state, except for memory, which is
placed in self-refresh mode to retain its contents. 
这种状态提供非常有效的节能。除了内存要自刷新以保留它的内容，系统中
所有东西都进入低功耗状态。




System and device state is saved and kept in memory. All devices are
suspended and put into D3. In many cases, all peripheral buses lose
power when entering STR, so devices must be able to handle the
transition back to the On state. 
系统和设备状态被保存在内存中。所有设备暂停并进入D3状态。在许多情况下，
所有外围总线在进入STR时断电，所以设备必须能处理回到开状态的转换。


For at least ACPI, STR requires some minimal boot-strapping code to
resume the system from STR. This may be true on other platforms. 
为了最小的ACPI，STR需要一些最低限度的开机代码以恢复从STR恢复系统。在其他平台也可能是
这样的。


State:          Suspend-to-disk
ACPI State:     S4
String:         "disk"


This state offers the greatest power savings, and can be used even in
the absence of low-level platform support for power management. This
state operates similarly to Suspend-to-RAM, but includes a final step
of writing memory contents to disk. On resume, this is read and memory
is restored to its pre-suspend state. 
此状态提供最好的节能，并且甚至能在缺乏低级平台电源管理支持时使用。此状态
操作和Suspend-to-RAM的操作很想。在恢复方面，被读取并且内存恢复到暂停之前
的状态。


STD can be handled by the firmware or the kernel. If it is handled by
the firmware, it usually requires a dedicated partition that must be
setup via another operating system for it to use. Despite the
inconvenience, this method requires minimal work by the kernel, since
the firmware will also handle restoring memory contents on resume. 
STD能通过固件或内核来处理。如果通过固件来处理，它通常需要专用的分区，要使用
此分区必须通过另一个操作系统来设置。尽管不方便，这个方法只需要最小的内核工作
量，因为固件也会处理内存内容的恢复工作。


For suspend-to-disk, a mechanism called 'swsusp' (Swap Suspend) is used
to write memory contents to free swap space. swsusp has some restrictive
requirements, but should work in most cases. Some, albeit outdated,
documentation can be found in Documentation/power/swsusp.txt.
Alternatively, userspace can do most of the actual suspend to disk work,
see userland-swsusp.txt.
对于挂起到磁盘，有一个被叫做'swsusp' (Swap Suspend)的机制，此机制向内存写入
内容来释放交换空间。swsusp有一些限制性的要求。但是在大部分情况下能工作。
一些虽然过时了的文档能在Documentation/power/swsusp.txt找的到。
另外，用户空间（userspace）能做大部分实际挂起到磁盘的工作，参见userland-swsusp.txt。




Once memory state is written to disk, the system may either enter a
low-power state (like ACPI S4), or it may simply power down. Powering
down offers greater savings, and allows this mechanism to work on any
system. However, entering a real low-power state allows the user to
trigger wake up events (e.g. pressing a key or opening a laptop lid).
一旦内存状态被写入到磁盘，系统可能进入低功耗状态（如ACPI S4），或是直接
断电。断电提供最大限度的节能，并且允许此机制在任何系统上工作。然而，进入
真正的低功耗状态允许用户唤醒事件（例如按下一个键或是打开笔记本电脑的盖子）。