The SoC vendor might provide you with the USB function lower filter driver for charger detection. For more information, see Developing Windows drivers for USB function controllers.
You can write a custom client driver for your function controller by using USB function controller client driver programming interfaces. Microsoft provides in-box client drivers for Synopsys USB 3.0 and ChipIdea USB 2.0 controllers. The USB function controller class extension supports MTP (Media Transfer Protocol) and charging using BC 1.2 chargers. The USB device-side drivers service the function/device/peripheral. In another system, the driver stack may not get loaded because dual role is not supported. In the preceding example, USB role switching is handled in the firmware of the system and USB Role Switch driver stack is not loaded.
Here is an example of a system with an embedded controller. Drivers for supporting USB Type-C components for systems with embedded controllers If your UCSI-compliant hardware uses a transport other than ACPI, you need to write a UCSI client driver. If your design includes an embedded controller with ACPI transport, implement UCSI in your system's BIOS/EC and load the in-box UCSI driver (UcmUcsiCx.sys and UcmUcsiAcpiClient.sys). Microsoft provides a USB Type-C Connector System Software Interface (UCSI) specification-compliant driver for ACPI transport.
0 kommentar(er)
