In the vendor-supplied AVStrMiniDeviceStart, AVStream minidrivers that support hardware should first parse the resource list and then call IoConnectInterrupt to register an interrupt service routine (ISR).
Additional steps are required if your driver supports direct memory access (DMA). If your driver implements DMA, see AVStream DMA Services.
If more than one application might build a filter graph simultaneously using your device, you must take care to prevent interference between graphs. Specifically, if you construct a graph in an application using the device, you must not interfere with an application which is using the device in a non-stop state.
You can avoid interference by loading microcode after the graph transitions into KSSTATE_ACQUIRE. This will protect a currently running graph because a new graph will not transition into KSSTATE_ACQUIRE while another graph is currently running. To receive notification of pin state changes, supply an AVStrMiniPinSetDeviceState callback routine in the KSPIN_DISPATCH structure.
To minimize graph start-up time, however, you may want to load microcode before the graph reaches KSSTATE_ACQUIRE. In this case, consider loading microcode in a low priority background thread during boot. This solution does not interfere with other applications, reduces graph start time, and should not lengthen boot time if done asynchronously.
After boot, however, do not reload microcode or manipulate hardware registers until the graph reaches KSSTATE_ACQUIRE.
To see how connection of a new graph can interfere with a running graph, consider a video capture device that supports encoding and decoding, but only performs one of these tasks at a time. The minidriver exposes an encode filter and a decode filter.
An application builds a filter graph containing the encode filter. The minidriver loads microcode for encoding at pin connection time. The filter graph starts and the hardware begins encoding.
While the hardware is encoding, another application places a decode filter in a filter graph. When the decode pins are connected, before the pins change state into KSSTATE_ACQUIRE, the minidriver attempts to configure the hardware for decoding. This reconfiguration interferes with the currently active encode graph and may result in a driver instability.