USB4 Systems Support All Type-C® Connectors
Verifies that systems supporting USB4 do so on all USB Type-C® connectors.
Description
Systems that support USB4 must do so on all user-accessible USB Type-C® connectors or clearly mark the connectors to indicate to the user which connectors support USB4. Consumers will expect their USB4 devices to just work with their PC or host device that supports USB4 and may plug it into any matching USB Type-C® connector on their system. It is strongly encouraged to support USB4 on all user-accessible USB Type-C® connectors so that the user experience is consistent and seamless. If USB4 support is not possible, the system must clearly indicate which are compatible with USB4 peripherals.
Test details
| Specifications |
|
| Platforms |
|
| Supported Releases |
|
| Expected run time (in minutes) | 5 |
| Category | Development and Integration |
| Timeout (in minutes) | 5 |
| Requires reboot | False |
| Requires special configuration | False |
| Type | development |
Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic:
More information
Parameters
| Parameter name | Parameter description | Default value | Required? | Settable? |
|---|---|---|---|---|
| USB4TypeCPortsVisuallyMarked | Set to true if there are Type-C® ports on the system which do not support USB4 and are clearly marked as such. | False | False | True |
Enhancement scenarios
All USB Type-C® ports are functionally identical to the user or are clearly marked to avoid user frustration.
Additional Notes
Every external Type-C® port (described as a Type-C® connector, user visible and connectable via ACPI UPC and PLD) must be USB4 capable, i.e. have a valid USB4 host router mapping via ACPI _DSD, unless visibly marked as a non-USB4 Type-C® port.
If there are any such Type-C® ports which are not USB4 capable and they are all marked as such, the test will accept an HLK parameter, USB4TypeCPortsVisuallyMarked, which can be set to True.
Troubleshooting
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.