Lines Matching +full:power +full:- +full:power +full:- +full:management
6 .TH POWER 9E "Dec 12, 2003"
8 power \- power a device attached to the system
17 \fBint prefix\fR\fBpower\fR(\fBdev_info_t\fR \fI*dip\fR, \fBint\fR \fIcomponent\fR, \fBint\fR \fIle…
51 Desired component power level.
57 The \fBpower\fR(9E) function is the device-specific Power Management entry
59 power level of \fIcomponent\fR to \fIlevel\fR.
62 The \fIlevel\fR argument is the driver-defined power level to which the
63 component needs to be set. Except for power level \fB0\fR, which is interpreted
69 power-managed. The interpretation of \fIcomponent\fR is entirely up to the
73 When a requested power transition would cause the device to lose state, the
74 driver must save the state of the device in memory. When a requested power
78 If a requested power transition for one component requires another component to
79 change power state before it can be completed, the driver must call
81 \fBpower\fR(9E) entry point must support being re-entered.
84 If the system requests an inappropriate power transition for the device (for
85 example, a request to power down a device which has just become busy), then the
86 power level should not be changed and power should return \fBDDI_FAILURE\fR.
90 The \fBpower()\fR function returns:
97 Successfully set the power to the requested \fIlevel\fR.
106 Failed to set the power to the requested \fIlevel\fR.
112 The \fBpower()\fR function is called from user or kernel context only.
139 \fIUsing Power Management\fR