Pilote de lecteur WDM

Required routines

Les routines suivantes sont requises par un pilote de lecteur WDM.

DriverEntry

Initialise l’objet de pilote et la table de distribution.

AddDevice

Crée un objet d’appareil pour le lecteur de carte à puce. In addition, AddDevice can call any of the following driver library routines:

• SmartcardInitialize (WDM) to complete driver initialization. Calling this routine in AddDevice is obligatory.
• SmartcardLogError (WDM) to log an error. Drivers must call this routine in AddDevice if SmartcardInitialize (WDM) fails.
• SmartcardCreateLink (WDM) to create a symbolic link for the reader device in the registry.

Unload

Supprime le pilote du système.

DispatchCreate

-and-

DispatchClose

Supports IRP_MJ_CREATE and IRP_MJ_CLOSE<, respectively. To establish a connection to the reader, the resource manager sends IRP_MJ_CREATE to the reader driver. To sever the connection, the resource manager sends IRP_MJ_CLOSE.

DispatchCleanup

Supports IRP_MJ_CLEANUP, which the resource manager sends to the reader driver to cancel pending I/O requests.

DispatchPnP

Supports IRP_MJ_PNP

DispatchPower

Supports IRP_MJ_POWER.

DispatchDeviceControl

Supports IRP_MJ_DEVICE_CONTROL and is the main entry point for smart card requests. Upon receiving IRP_MJ_DEVICE_CONTROL, DispatchDeviceControl must immediately call SmartcardDeviceControl (WDM), which is the smart card driver library routine that handles device-control requests. L’exemple de code suivant montre comment appeler cette routine de bibliothèque à partir d’un pilote WDM :

NTSTATUS
DriverDeviceControl(
    PDEVICE_OBJECT DeviceObject,
    PIRP Irp
    )
{
    PDEVICE_EXTENSION deviceExtension = DeviceObject -> DeviceExtension;

    return SmartcardDeviceControl(
        &(deviceExtension->SmartcardExtension),
        Irp
        );

If it is unable to handle the particular IOCTL that is indicated in the call, SmartcardDeviceControl will call the driver's callback for unknown IOCTL requests.