Lines Matching +full:power +full:- +full:power +full:- +full:management
8 pm \- Power Management driver
18 The Power Management ( \fBpm\fR) driver provides an interface for applications
19 to configure devices within the system for Power Management. The interface is
22 .SS "Power Management Framework"
25 The Power Management framework model allows the system to be viewed as a
27 the smallest power manageable units. The device driver controls the definition
28 of a device's power manageable components.
31 A component can either be \fBbusy\fR or \fBidle\fR at the current power level.
32 Normally, the Power Management framework takes an \fBidle\fR component to the
33 next lower power level. The Power Management framework uses two factors to
37 device to be power managed before it can be power managed. Dependencies occur
39 be managed unless all the devices it depends upon are first power managed.
42 Using the commands below, an application may take control of the Power
43 Management of a device from the Power Management framework driver and manage
44 the transition of device power levels directly.
56 int value; /* power level, threshold value, or count */
57 void *data; /* command-dependent variable-sized data */
83 Non-negative integer specifying which component is being configured. The
93 Non-negative integer specifying the threshold value in seconds or the desired
94 power level, or the number of levels being specified.
103 Pointer to a buffer which contains or receives variable-sized data, such as the
126 The device named by \fIphyspath\fR is disabled from being power managed by the
127 framework. The caller will power manage the device directly using the
130 needs to have its power level changed either because its driver calls
133 device that is changing power level or a device that this device depends on is
134 changing power level, then the power level change of the device will be blocked
145 Device already disabled for Power Management by framework.
167 \fBPM_DIRECT_PM\fR command) is re-enabled for Power Management by the
189 These commands allow the process that is directly power managing a device to be
190 notified of events that could change the power level of the device. When such
209 int old_level; /* power level changing from */
210 int new_level; /* power level changing to */
219 were not directly power managed by the caller. The caller is responsible for
223 directly power managed device has called \fBpm_power_has_changed\fR(9F) due to
224 the device changing power on its own. It is provided to allow the caller to
225 track the power state of the device.
248 \fBPM_DIRECT_PM\fR command) is set to power level \fIvalue. \fRIf all
250 is non-zero and some device has a dependency on this device, then all
251 components of that device will be brought to full power before this command
254 PM_SET_CURRENT_POWER is issued against a device, the resulting power change is
264 Device component out of range, or power level < 0.
273 Failed to power device or its ancestors or the devices on which this device has
298 The highest supported power level of component \fIcomponent\fR of the device
309 The current power level of component \fIcomponent\fR of the device named by
319 Device component power level is not currently known.
337 issues a \fBPM_SET_CURRENT_POWER\fR command to reduce the power level of an
366 Device is not power manageable, or device is not configured.
398 \fBpower.conf\fR(4), \fBattributes\fR(5), \fBattach\fR(9E), \fBdetach\fR(9E),
399 \fBpower\fR(9E), \fBpm_busy_component\fR(9F), \fBpm_idle_component\fR(9F),