Lines Matching +full:power +full:- +full:power +full:- +full:management

6 .TH POWER.CONF 4 "Feb 27, 2009"
8 power.conf \- Power Management configuration information file
12 \fB/etc/power.conf\fR
18 The \fBpower.conf\fR file is used by the Power Management configuration program
19 \fBpmconfig\fR(1M), to initialize the settings for Power Management. If you
25 allowed by this file. For ease-of-use, it is recommended that you use
27 for information on disabling Power Management.
30 Power Management addresses two specific management scenarios: management of
31 individual devices and management of the whole system. An individual device is
32 power managed if the device supports multiple power levels and if the device
33 driver uses Power Management interfaces provided by the kernel to save device
34 power when the device is idle.
37 All entries in the \fBpower.conf\fR file are processed in the order that they
39 .SS "Automatic Device Power Management"
42 Devices with drivers that use the automatic device Power Management interfaces
43 are automatically power managed if the \fBautopm\fR entry is enabled. The
45 \fBpm-components\fR property describes the Power Management model of a device
46 driver to the Power Management framework. See \fBpm-components\fR(9P) for more
50 When a component has been idle at a given power level for its threshold time,
51 the power level of the component is reduced to the next lower power level of
53 component is power-managed independently.
56 Default thresholds for components of automatically power managed devices are
57 computed by the Power Management framework based on the system idleness
69 system-threshold \fIthreshold\fR
76 system-threshold \fBalways-on\fR
84 (defaulting to seconds if only a number is given). If \fBalways-on\fR is
85 specified, then by default, all devices are left at full power.
88 The \fBsystem-threshold\fR entry is applicable to CPU Power Management only
89 when CPU Power Management has been configured to operate in poll-mode, which is
93 If a system has power manageable CPUs, these can be managed independently of
98 cpu-threshold \fIthreshold\fR
105 cpu-threshold \fBalways-on\fR
113 (defaulting to seconds if only a number is given). If \fBalways-on\fR is
114 specified, then by default, all CPUs are left at full power.
117 The \fBcpu-threshold\fR keyword is used only when CPU Power Management has been
118 configured to operate in poll-mode, which is expressed through the \fBcpupm\fR
122 If no \fBcpu-threshold\fR entry is specified, then the system idleness
126 To override the default device component thresholds assigned by the Power
127 Management framework, a \fBdevice-thresholds\fR entry can be used. A
128 \fBdevice-thresholds\fR entry sets thresholds for a specific automatically
129 power-managed device or disables automatic Power Management for the specific
133 A \fBdevice-thresholds\fR entry has the form:
137 device-thresholds \fIphys_path\fR \fI(threshold ...) ...\fR
147 device-thresholds \fIphys_path\fR \fIthreshold\fR
157 device-thresholds \fIphys_path\fR \fBalways-on\fR
173 with a default to seconds, to spend idle at the corresponding power level
174 before power is reduced to the next lower level of that component. Parentheses
178 idle in the highest power level of the component before going to the
179 next-to-highest level, while the first (leftmost) number represents the time to
180 be idle in the next-to-lowest power level before going to the lowest power
185 device (by means of \fBpm-components\fR(9P) property), or the number of
186 thresholds in a group is not one less than the number of power levels the
192 Buffer\fR and \fBMonitor\fR. Component \fBFrame Buffer\fR has two power levels:
193 \fBOff\fR and \fBOn\fR. Component \fBMonitor\fR has four power levels:
197 The following \fBdevice-thresholds\fR entry:
201 device-thresholds \fI/pci@f0000/xfb@0 (0) (3m 5m 15m)\fR
224 In the third form above, all components of the device are left at full power.
227 Device Power Management entries are only effective if there is no user process
229 control frame buffers. The entries in the \fBpower.conf\fR file are effective
234 if none of its components might have their power levels reduced unless all
240 device-dependency \fIdependent_phys_path phys_path [ phys_path ... ]\fR
251 physically connected to the power managed device (for example, the display and
262 device-dependency-property \fIproperty\fR \fIphys_path\fR [\fIphys_path\fR ...]
276 boolean property named \fBremovable-media\fR is kept up when the console
277 framebuffer is up. See \fBremovable-media\fR(9P).
283 # (See removable-media(9P))
285 device-dependency-property removable-media /dev/fb
291 An \fBautopm\fR entry can be used to enable or disable automatic device Power
292 Management on a system-wide basis. The format of the \fBautopm\fR entry is:
311 Memorandum of Understanding #3\fR have automatic device Power Management
322 Automatic device Power Management is started when this entry is encountered.
331 Automatic device Power Management is stopped when this entry is encountered.
336 A \fBcpupm\fR entry can be used to enable or disable Power Management of CPUs
337 on a system-wide basis, independent of \fBautopm\fR. The format of the
355 CPU Power Management is started when this entry is encountered.
370 \fB\fBevent-mode\fR\fR
373 CPU power state transitions is driven by thread scheduler/dispatcher events.
374 The \fBcpu-threshold\fR, and \fBsystem-threshold\fR keywords are not used for
381 \fB\fBpoll-mode\fR\fR
384 The Power Management framework polls the idleness of the system's CPUs, and
385 manages their power once idle for the period of time specified by either the
386 \fBsystem-threshold\fR or \fBcpu-threshold\fR.
397 CPU Power Management is stopped when this entry is encountered.
403 or disable automatic use of power saving cpu idle states. The format of the
422 Advanced cpu idle power saving features are enabled on hardware which supports
423 it. On X86 systems this can translate to the use of ACPI C-States beyond C1.
432 Enables the system to automatically use idle cpu power saving features.
441 The system does not automatically use idle cpu power saving features. This
443 power.
452 It the \fBcpu_deep_idle\fR keyword is absent from \fBpower.conf\fR the behavior
458 Once every device is at its lowest possible power state, additional power
467 override this default, an S3-support entry (of the format S3-support
479 an \fBS3-support enable\fR entry does not support entry into S3, the attempt
481 of a system enabled via an S3-support entry contains bugs, the system can be
498 automatic entry into the S3 state. When in the S3 state, the power button,
518 enabled. Non-Sun systems do not. See \fBNOTES\fR for more information.
528 every device is at its lowest power state.
540 .SS "System Power Management"
543 The system Power Management entries control Power Management of the entire
544 system using the suspend-resume feature. When the system is suspended, the
545 complete current state is saved on the disk before power is removed. On reboot,
551 the suspend-resume feature by an entry of the following form:
740 \fBExample 1 \fRDisabling Automatic Device Power Management
743 To disable automatic device Power Management, change the following line in the
744 \fB/etc/power.conf\fR file
770 You can also use \fBdtpower\fR to disable automatic device Power Management.
792 \fBpmconfig\fR(1M), \fBpowerd\fR(1M), \fBsys-unconfig\fR(1M), \fBuadmin\fR(2),
794 \fBpm\fR(7D), \fBpm-components\fR(9P), \fBremovable-media\fR(9P)
811 unconfigured by \fBsys-unconfig\fR(1M).
827 prtconf -pv | grep -i energystar
837 System Power Management ( suspend-resume) is currently supported only on a
840 system Power Management. See \fBuname\fR(2) to programmatically determine if
841 the machine supports suspend-resume.