UMDF to KMDF driver communication; best practice?

NTDEV
1

What is the best way to communicate between a UMDF v2 driver and a KMDF driver?

I have a functional KMDF USB driver that I can do ReadFile and WriteFile on. I am attempt to keep the kernel driver as simple as possible.

To work with a legacy application I have a separate UMDF v2 Virtual COM Port (VCP) driver. This will contain any buffering; implement the WaitOnEvent and the other stuff specific to COM ports. Another reason for splitting the driver is so the COM port remains present when the USB device is not attached.

Should I be using CreateFile, ReadFile and WriteFile in the UMDF v2 driver using overlapped I/O, as I would do when writing applications; or a different approach?

I have read older discussions and documentation online, but either about kernel drivers or UMDF v1. Not entirely sure what is valid, or appropriate, for UMDF v2.

Thanks,
Mark

2

If what you want to do are well-patterned as reads and writes, then yes… this is the right thing to do.

Alternatively, you can use the famous “inverted call model”: https:</https:>

Peter
OSR
@OSRDrivers