If power management is supported, and detach(9E) and attach(9E) are used as in Example 53, detach Routine Implementing DDI_SUSPEND and Example 54, attach9E Routine Implementing DDI_RESUME, then access to the device can be made from user context, for example, from read(2), write(2), and ioctl(2).
The following example demonstrates this approach. The example assumes that the operation about to be performed requires a component component that is operating at power level level.
Example 55 Device Accessmutex_enter(&xsp->mu);
/*
* Block command while device is suspended by DDI_SUSPEND
*/
while (xsp->xx_suspended)
cv_wait(&xsp->xx_suspend_cv, &xsp->mu);
/*
* Mark component busy so xx_power() will reject attempt to lower power
*/
xsp->xx_busy[component]++;
if (pm_busy_component(dip, component) != DDI_SUCCESS) {
xsp->xx_busy[component]--;
/*
* Log error and abort
*/
}
if (xsp->xx_power_level[component] < level) {
mutex_exit(&xsp->mu);
if (pm_raise_power(dip, component, level) != DDI_SUCCESS) {
/*
* Log error and abort
*/
}
mutex_enter(&xsp->mu);
}
The code fragment in the following example can be used when device operation completes, for example, in the device's interrupt handler.
Example 56 Device Operation Completion/*
* For each command completion, decrement the busy count and unstack
* the pm_busy_component() call by calling pm_idle_component(). This
* will allow device power to be lowered when all commands complete
* (all pm_busy_component() counts are unstacked)
*/
xsp->xx_busy[component]--;
if (pm_idle_component(dip, component) != DDI_SUCCESS) {
xsp->xx_busy[component]++;
/*
* Log error and abort
*/
}
/*
* If no more outstanding commands, wake up anyone (like DDI_SUSPEND)
* waiting for all commands to be completed
*/