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

6 .TH PM-COMPONENTS 9P "Jan 6, 2004"
8 pm-components \- Power Management device property
12 A device is power manageable if the power consumption of the device can be
13 reduced when it is idle. In general, a power manageable device consists of a
14 number of power manageable hardware units called components. Each component is
15 separately controllable and has its own set of power parameters.
18 An example of a one-component power manageable device is a disk whose spindle
19 motor can be stopped to save power when the disk is idle. An example of a
20 two-component power manageable device is a frame buffer card with a connected
21 monitor. The frame buffer electronics (with power that can be reduced when not
23 which can enter in a lower power mode when not in use. The combination of frame
27 In the Power Management framework, all components are considered equal and
33 The \fBpm-components\fR property describes the Power Management model of a
34 device driver to the Power Management framework. It lists each power manageable
35 component by name and lists the power level supported by each component by
40 has successfully attached, or upon the first call into Power Management
45 \fBpm-components\fR is a string array property. The existence of the
46 \fBpm-components\fR property indicates that a device implements power
47 manageable components and describes the Power Management model implemented by
48 the device driver. The existence of \fBpm-components\fR also indicates to the
49 framework that device is ready for Power Management if automatic device Power
50 Management is enabled. See \fBpower.conf\fR(4).
53 The \fBpm-component\fR property syntax is:
56 …-components="NAME=component name","numeric power level=power level name",  "numeric power level=po…
65 numeric value (can be decimal or 0x <hexadecimal number>) of a power level the
67 name for that power level. Again, the names should be descriptive, such as
71 power levels the component supports.
75 number as interpreted by the driver's \fBpower\fR(9E) routine. (Components are
76 numbered sequentially from 0). The power levels must be listed in increasing
77 order of power consumption. Each component must support at least two power
78 levels, or there is no possibility of power level transitions. If a power level
79 value of 0 is used, it must be the first one listed for that component. A power
80 level value of 0 has a special meaning (off) to the Power Management framework.
84 An example of a \fBpm-components\fR entry from the \fB\&.conf\fR file of a
85 driver which implements a single power managed component consisting of a disk
86 spindle motor is shown below. This is component 0 and it supports 2 power
91 pm-components="NAME=Spindle Motor", "0=Stopped", "1=Full Speed";
115     if (ddi_prop_update_string_array(DDI_DEV_T_NONE, dip, "pm-components",
126 Component 0 is the frame buffer electronics which supports four different power
127 levels. Component 1 represents the state of Power Management of the attached
132 pm-components="NAME=Frame Buffer", "0=Off"
159 \fBpower.conf\fR(4), \fBpm\fR(7D), \fBattach\fR(9E), \fBdetach\fR(9E),