Interlocked plug and play with power management for operating systems

• US 20050246719A1
• Filed: 04/28/2004
• Published: 11/03/2005
• Est. Priority Date: 04/28/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Oshins, Jacob, Holan, Doron
• Granted Patent: US 7,308,586 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 1/3203 Power management, i.e. event-based initiation of a power-saving mode
• CPC Class Codes: G06F 1/3287 by switching off individual functional units in the computer system
• CPC Class Codes: G06F 13/102 where the programme performs an interfacing function, e.g. device driver G06F13/105 takes precedence; scheduling within device drivers G06F9/52; contention policies within device drivers G06F9/4881
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The present invention provides a unified layer for Plug and Play (PnP) components and power management components while relieving device drivers from system-level complexities associated with implementing PnP and/or power management functionality. The layer operates at a level between low-level device drivers and more complex operating system tasks. The subject invention simplifies designing device drivers having proper power management support by creating an infrastructure that allows a device driver to operate within a driver framework or model and without having to process Plug-and-Play or Power Management I/O Request Packets (IRPs) directly.

Claims

1. A method for computer domain power management, comprising:

providing a Plug and Play (PNP) state machine to track PNP events;

providing a Power state machine to track device driver events;

providing a Power Policy state machine to track system power events; and

providing at least one Application Programming Interface (API), function, or callback to interact with the state machines, the device driver, or an operating system framework.

2. The method of claim 1, the API, function, or callback further comprising at least one of DeviceInitSetPowerCapabilities and DeviceInitSetPowerPolicyOwnership.

3. The method of claim 1, the API, function, or callback further comprising at least one of DeviceSetFailed, DeviceInitRegisterPnpStateChangeCallback, DeviceInitRegisterPowerStateChangeCallback, DeviceInitRegisterPowerPolicyStateChangeCallback, and DeviceSetStaticStopRemove.

4. The method of claim 1, the API, function, or callback further comprising at least one of EvtDeviceD0Entry, EvtDeviceD0Exit, and EvtDevicePrepareHardware.

5. The method of claim 1, the API, function, or callback further comprising at least one of EvtDeviceContextCleanup, and EvtDeviceSelfManagedIoCleanup.

6. The method of claim 1, the API, function, or callback further comprising at least one of EvtDeviceSelfManagedIoInit, EvtDeviceSelfManagedIoSuspend, EvtDeviceSelfManagedIRestart, and EvtDeviceSelfManagedStop.

7. The method of claim 1, the API, function, or callback further comprising at least one of EvtDeviceSurpriseRemoval, and EvtDeviceRelaeaseHardware.

8. The method of claim 1, the API, function, or callback further comprising at least one of DeviceSetIdleTimeout, DevicePowerReference, DevicePowerDereference, DeviceSetDeepestIdleState.

9. The method of claim 1, the API, function, or callback further comprising at least one of EvtDeviceWakeArmS0, EvtDeviceWakeDisarmS0, and EvtDeviceWakeTriggeredS0.

10. The method of claim 1, the API, function, or callback further comprising at least one of EvtDeviceWakeArmSx, EvtDeviceWakeDisarmSx, and EvtDeviceWakeTriggeredSx.