The required driver depends on the controller config.
One main thing about USB drivers is the VID and PID codes embedded in the device firmware, these codes need to be related to the codes in the .inf file pointing to a driver.
For example, I recently build a PIC USB device operating in CDC mode. This is a simple USB port serial emulation. From the Microchip driver, Windows will see and treat the device as a standard serial port. The .inf file is just pointing to a standard Windows driver, usbser.sys in this case.
When I got a PID and VID code for my product, these were included in my device firmware. I then edited the .inf file with the same PID and VID codes, so Windows could validate the .inf file was related to the device being installed. I did not change the line defining witch driver to load.
In your case, the evaluation kit for a compatible chip contains:
This may, or may not be a good starting point for you. The evaluation board seems to be capable of working in serial port emulation mode from a provided example, witch could be the same as yours.
Best may be to search for a driver for the device in which the controller in embedded and skip the reverse engineering, then again, this is an engineering forum...
__________________
''What the hell has my a** got to do with magic?" Don Quixote