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

8 attach \- Attach a device to the system, or resume it
48 The \fBattach\fR(9E) function is the device-specific initialization entry
68 At attach time, all components of a power-manageable device are assumed to be
70 required component(s) to a known power level. The \fBpm_raise_power\fR(9F)
71 function can be used to set the power level of a component. This function must
72 not be called before data structures referenced in \fBpower\fR(9E) have been
83 the hardware state of a device (power may have been removed from the device),
86 restore the state of the device except for the power level of components.
89 If the device driver uses the automatic device Power Management interfaces
90 (driver exports the \fBpm-components\fR(9P) property), the Power Management
91 framework sets its notion of the power level of each component of a device to
100 If the driver can determine the power level of the component without having
101 to power it up (for example, by calling \fBddi_peek\fR(9F) or some other
102 device-specific method) then it should notify the power level to the framework
108 The driver must also set its own notion of the power level of the component
112 sufficient time, the framework will call into the driver's \fBpower\fR(9E)
116 request to set the power level of the component, since it cannot make any
117 assumption about what power level the component has (or it should have called
121 loading firmware so that it can detect hot-plug events).
164 \fBcpr\fR(7), \fBpm\fR(7D), \fBpm\fR(9P), \fBpm-components\fR(9P),
166 \fBpower\fR(9E), \fBprobe\fR(9E), \fBddi_add_intr\fR(9F),