| UID | title | description | old-location | tech.root | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:usbspec._USB_STRING_DESCRIPTOR |
_USB_STRING_DESCRIPTOR (usbspec.h) |
The USB_STRING_DESCRIPTOR structure is used by USB client drivers to hold a USB-defined string descriptor. |
buses\usb_string_descriptor.htm |
usbref |
05/07/2018 |
|
*PUSB_STRING_DESCRIPTOR, PUSB_STRING_DESCRIPTOR, PUSB_STRING_DESCRIPTOR structure pointer [Buses], USB_STRING_DESCRIPTOR, USB_STRING_DESCRIPTOR structure [Buses], _USB_STRING_DESCRIPTOR, buses.usb_string_descriptor, usbspec/PUSB_STRING_DESCRIPTOR, usbspec/USB_STRING_DESCRIPTOR, usbstrct_b0740c7e-9042-4426-be26-20b8620a0e7e.xml |
usbspec.h |
Usbioctl.h |
Windows |
Windows |
USB_STRING_DESCRIPTOR, *PUSB_STRING_DESCRIPTOR |
|
|
|
|
|
The USB_STRING_DESCRIPTOR structure is used by USB client drivers to hold a USB-defined string descriptor. The members of this structure are described in the Universal Serial Bus 3.1 Specification available at USB Document Library. See section 9.6.9.
Specifies the length, in bytes, of the descriptor.
Specifies the descriptor type. Must always be USB_STRING_DESCRIPTOR_TYPE.
Pointer to a client-allocated buffer that contains, on return from the host controller driver, a Unicode string with the requested string descriptor.
This structure is used to hold a device, configuration, interface, class, vendor, endpoint, or device string descriptor. The string descriptor provides a human-readable description of the component.
Strings returned in bString are in Unicode format and the contents of the strings are device-defined.