This is how I set up a continuous reader and I start the continuous reader with WdfIoTargetStart() in D0Entry and do a WdfIoTargetStop() in D0 Exit.
WDF_USB_CONTINUOUS_READER_CONFIG_INIT(&contReaderConfig,
My_EvtUsbInterruptPipeReadComplete,
fdoData, // Context
2*1024); // TransferLength
contReaderConfig.EvtUsbTargetPipeReadersFailed =
My_EvtUsbInterruptReadersFailed;
//
// Reader requests are not posted to the target automatically.
// Driver must explictly call WdfIoTargetStart to kick start the
// reader. In this sample, it’s done in D0Entry.
// By defaut, framework queues two requests to the target
// endpoint. Driver can configure up to 10 requests with CONFIG macro.
//
status = WdfUsbTargetPipeConfigContinuousReader(fdoData->InterruptPipe,
&contReaderConfig);
Thanks,
Vidya
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@microsoft.com
Sent: Monday, May 11, 2009 4:01 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] WDF_USB_CONTINUOUS_READER_CONFIG_INIT
cancelling out the two read requests that remained outstanding(pending).
Two more things:
- By outstanding(pending) you mean you’ve already formatted and submitted the requests, right?
- Did you call WdfIoTargetStop() from your D0Exit?
Regards,
Tanya
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer