Power delivery

Support for charging a USB Type-C system by using legacy chargers (<7.5W), USB Type-C chargers (<15W), Power Delivery chargers (100W+)

For Windows 10 Mobile systems,

• Charging from legacy chargers is handled by the USB device-side drivers in Windows.
• Charging from USB Type-C chargers (including those that implement Power Delivery), is handled by the USB connector manager drivers: USB connector manager class extension (UcmCx) and its client driver for the connector. The client driver communicates with the hardware to determine the charging policy and forwards that UcmCx, which further sends it to the charging arbitration driver (CAD). CAD selects the charging source to use.

For Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) systems,

• Charging from legacy chargers is not recommended, as they are not powerful enough to charge desktop systems.
• Charging for USB Type-C chargers is handled by USB connector manager class extension (UcmCx) and its client driver for the connector. The system does not currently specify which power source to use and how much power to consume.

You must determine the charging policy in your hardware, firmware, and client driver. Charging policy mainly includes:

• Is the system a power source (provider) or power sink (consumer)?
• How much power should the system consume?​
• Which power source (charger) should be used if there are multiple power sources available (such as chargers)?​

For power delivery-compliant chargers, the hardware must negotiate a power contract, which includes the voltage and current.​ The negotiated power contract must be forwarded to the system through the USB connector manager class extension (UcmCx) or the USCI driver for appropriate action.

If a slow charger is connected to the system, the system must be notified through UcmCx or UCSI.

To support legacy proprietary high-voltage or high-current charging mechanisms, an additional filter driver must be written for Microsoft’s in-box USB Function driver that detects the proprietary charger and reports it to the in-box driver.

Connecting USB devices and peripherals

Ability of a Windows system (desktop and mobile) to connect USB devices/peripherals

Windows 10 for desktop editions supports most device classes. The device drivers and their installation files are included in Windows

Devices that run Windows 10 Mobile can connect and interact with USB devices/peripherals​ through a set of in-box drivers. The operating system supports a subset of device classes.

See, USB device class drivers included in Windows.

If your system wants to connect to a custom USB device for which Windows does not include a driver, you can choose to load the generic driver (Winusb.sys) or write a driver. For guidance, see Choosing a driver model for developing a USB client driver.

We recommend that you write a single driver that runs on Windows 10 for desktop editions and Windows 10 Mobile. For more information, see Getting Started with Universal Windows drivers.

To write an application that communicates the device, use Windows Runtime APIs. For more information, see Talking to USB devices, start to finish (UWP app).

Connect to a non-USB device (e.g. monitor) using a USB Type-C connector.

Windows 10 is capable of detecting DisplayPort/DockPort devices if the hardware supports those alternate modes.

Windows 10 provides an in-box driver for a Billboard device and notifies the user if the Billboard device indicates that an error occurred.

In order for an alternate mode to work, your system and device must support the alternate mode in the hardware and firmware. Perform necessary tasks to negotiate the alternate mode and entering the mode. That is typically accomplished by muxing the wire on the USB Type-C connector to the alternate mode.

Display information about the error condition to help the user troubleshoot issues.

Windows 10 provides an in-box driver for Billboard devices and notifies the user if the Billboard device indicates an error.

The user might see an error notification, if:

• The alternate mode is not supported by the PC or phone running Windows 10.
• The alternate mode is not supported by the cable (if used).

Your Alternate Mode adapter or device must implement a Billboard device that indicates whether or not an Alternate Mode negotiation was successful.

If your alternate mode adapter or device implements other USB functionality, updating the contents of your Billboard descriptor will require you to disconnect and reconnect the device, possibly interrupting functionality (such as a file transfer, if your device is a USB mass storage device). To avoid that, the Billboard specification recommends that you use an integrated hub in your device, and have the Billboard device appear as a separate USB device on one of its ports.

For more information, see USB Device Class Definition for Billboard Devices specification.

Connect two Windows devices together​

When two Windows devices are connected together, the system determines the appropriate role that each of the devices should be in and performs role swap operations if needed.

To support this, Windows 10 can communicate with the dual role controller on the system through the USB role switch class extension framework. An inbox client driver for this framework is also provided for Synopsys dual role controllers.

For USB Type-C systems, the USB connector manager gets information about the roles initially assigned by the hardware port controllers.

The USB role switch stack and the USB connector manager stack communicate with the hardware to get the current role and swap the roles of the system’s port as needed.

Dual role ports must work with the operating system to make sure the right software stack (either Host or Function) is loaded at the right time.

Systems can be designed such that the dual-role USB port needs Windows to configure it to either Host or Function mode. These designs will need to use the USB role switch stack. If the system does not use a Synopsys or ChipIdea dual role controller, you will need to write a USB role switch client driver for the system’s dual role controller.

System can also be designed such that the firmware or the customer-supplied drivers configure the port as either a Host or Function port, depending on the device that is connected to the port. These designs will need to either implement this logic in the firmware, or will need to implement it in a USB connector manager client driver. In these systems, Windows will automatically load the correct software stack.

USB Type-C connector can be used as an audio jack.

The USB Type-C specification connector allows a USB Type-C connector to be used similar to a 3.5' analog audio jack by using the audio accessory mode. Windows 10 supports systems that implement USB Type-C support for audio accessories by detecting the accessory as a regular 3.5' analog audio device.