Поделиться через


Required and Optional OIDs for Power Management (NDIS 5.1)

Note   NDIS 5. x has been deprecated and is superseded by NDIS 6. x. For new NDIS driver development, see Network Drivers Starting with Windows Vista. For information about porting NDIS 5. x drivers to NDIS 6. x, see Porting NDIS 5.x Drivers to NDIS 6.0.

For a miniport driver, supporting power management involves supporting power management object identifiers (OIDs). For a detailed description of how miniport drivers process queries and sets to OIDs, see Obtaining and Setting Miniport Driver Information and NDIS Support for WMI.

There are two levels of power management support for miniport drivers:

  1. A miniport driver can support its NIC making a transition between power states. This is the minimum level of power management support. For a description of device power states for NICs, see Device Power States for NICs.

  2. A miniport driver can also support one or more Network Wake-Up Events.

A miniport driver must support the following OIDs for its NIC to make a transition between power states:

  • OID_PNP_CAPABILITIES

    If the miniport driver returns NDIS_STATUS_SUCCESS in response to a query of this OID, NDIS treats a miniport driver as power management-aware. If the miniport driver returns NDIS_STATUS_NOT_SUPPORTED, NDIS treats the miniport driver as a legacy miniport driver that is not power management-aware.

  • OID_PNP_QUERY_POWER

    This OID specifies a device power state to which the NIC should prepare to transition. A miniport driver must always return NDIS_STATUS_SUCCESS in response to a query of OID_PNP_QUERY_POWER. By returning NDIS_STATUS_SUCCESS in response to this OID request, the miniport driver guarantees that it will transition the NIC to the specified device power state on receipt of a subsequent OID_PNP_SET_POWER request. The miniport driver, in this case, must do nothing to jeopardize the transition.

  • OID_PNP_SET_POWER

    This OID indicates that the NIC will transition to the indicated device power state. A miniport driver must prepare the NIC for the transition to the specified state before the driver returns NDIS_STATUS_SUCCESS. A miniport driver must always return NDIS_STATUS_SUCCESS in response to this OID.

To support network wake-up events, a miniport driver must also support the OID_PNP_ENABLE_WAKE_UPOID. Both protocol drivers and NDIS use this OID to enable a NIC's wake-up capabilities. For more information, see Enabling Wake-Up Events.

To support network wake-up frames (see Network Wake-Up Events), a miniport driver must also support the following OIDs that are related to wake-up events:

  • OID_PNP_ADD_WAKE_UP_PATTERN

    A protocol driver uses this OID to add a wake-up pattern to a list that either the NIC or miniport driver or both maintain.

  • OID_PNP_REMOVE_WAKE_UP_PATTERN

    A protocol driver uses this OID to delete a wake-up pattern that it previously specified with OID_PNP_ADD_WAKE_UP_PATTERN.

NDIS miniport drivers that support network wake-up events can optionally support the following statistical OIDs that are related to wake-up events:

  • OID_PNP_WAKE_UP_ERROR

    Protocol drivers query this OID to determine the number of false wake-ups signaled by the miniport driver's NIC.

  • OID_PNP_WAKE_UP_OK

    Protocol drivers query this OID to determine the number of valid wake-ups that are signaled by the miniport driver's NIC.

 

 

Send comments about this topic to Microsoft