I read the power(9e) man page, and I confess that I don't understand it, or even know if it applies to me. I'm dealing with a NIC which is pretty simple from a PM perspective. Do I need a dev_ops devo_power hook? Or do I just field DDI_SUSPEND/DDI_RESUME when passed to my attach/detach routines? The latter is what most other NIC drivers seem to do.
Right now I have simple suspend/resume routines hooked from DDI_SUSPEND/DDI_RESUME which *appear* to work when I do sudo uadmin 3 25 207, where 207 is my driver's major. However, according to the NIC, it was never told to change power states, so I'm worried my test coverage is less than complete. Is this uadmin command supposed to transition the device away from D0? Is that something I need to do myself? Is there a better uadmin number to use for the kind of testing I'm trying to do? How much (if any) of PCI config space will the system save for me when the device transitions to a low power state? Some OSes expect the driver to do this, and others will save everything for the driver. Others save the lower portions, but leave extended config space to be saved by the driver. Without uadmin actually lowering the power state, I can't tell how much of config space is getting restored for me, and I don't see where this is documented. BTW, I read http://blogs.sun.com/randyf/entry/testing_suspend_and_resume_for, and that had some great tips for testing. Many thanks for writing that (and I now know we both like belgian trappist ale). Thanks & sorry to be dense, Drew _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
