Introduction to Hardware Resources

After a user plugs in a PnP device, the driver that enumerates the device typically creates one or more logical configurations, which are combinations of hardware resources that the device can use. These configurations include the following:

  • A boot configuration that lists the hardware resources that the device requires when the system starts. (For PnP devices, this information is supplied by the BIOS.)

  • Additional configurations in which the device can operate. The driver groups these additional configurations in a resource requirements list. The PnP manager will eventually select resources from this list to assign to the device.

After the driver creates the logical configurations, it sends them to the framework, and the framework sends them to the PnP manager.

Next, the PnP manager determines which drivers the device requires and loads them if they are not already loaded. The PnP manager sends the device's hardware requirements list to the device's drivers for review. Function and filter drivers can modify this list and send it back to the PnP manager.

The PnP manager examines the modified hardware requirements list and determines which of the specified resources are actually available on the system. If the device requires resources that the PnP manager had previously assigned to another device, the PnP manager might attempt to redistribute resources among the system's devices.

Next, the PnP manager creates a resource list, which is a list of resources that the PnP manager intends to assign to the device. The PnP manager sends this list to the device's drivers for review. At this point, the function and filter drivers can remove resources from the list but they cannot add resources to it.

Finally, the PnP manager assigns resources to the device. The framework passes the resource list to the device's function and filter drivers, and the device's function driver performs any initialization that is necessary so that the device and driver can access the resources.

The following steps describe the process in more detail:

  1. A user plugs in a device.

  2. A bus driver detects the device and enumerates it.

  3. The framework calls the bus driver's EvtDeviceResourcesQuery callback function, which creates a resource list that describes the device's boot configuration.

  4. The framework calls the bus driver's EvtDeviceResourceRequirementsQuery callback function, which creates a resource requirements list for the device.

  5. The PnP manager determines which drivers the device requires and loads them, if they are not already loaded, to create a driver stack for the device.

  6. The PnP manager sends the device's resource requirements list to the driver stack for review. As the list travels down the driver stack, the framework calls each function and filter driver's EvtDeviceFilterRemoveResourceRequirements callback function. As the list travels back up the stack, the framework calls each function and filter driver's EvtDeviceFilterAddResourceRequirements callback function. Both of these callback functions can modify the resource requirements list.

  7. The PnP manager creates a resource list for the device and sends it to the driver stack for review. The framework calls each function and filter driver's EvtDeviceRemoveAddedResources callback function, which removes resources that the driver's EvtDeviceFilterAddResourceRequirements callback function added so the bus driver will not attempt to use them.

  8. The framework receives the final resource list from the PnP manager and stores it.

  9. If a driver calls WdfInterruptCreate to create interrupt objects, the framework finds interrupt resources in the resource list and assigns them to the interrupt objects.

  10. After the device has entered an uninitialized D0 state, the framework calls each driver's EvtDevicePrepareHardware callback function, passing raw and translated versions of the device's resource list as an input argument. The driver can save the resource list, which is valid until the framework calls the driver's EvtDeviceReleaseHardware callback function.

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft