menu "USB Host Library Test" orsource "$IDF_PATH/examples/common_components/env_caps/$IDF_TARGET/Kconfig.env_caps" config USB_HOST_TEST_CHECK_MANU_STR bool "Check manufacturer string descriptor" default y help USB Host tests that check string descriptors will check the manufacturer string descriptor of the connected device. config USB_HOST_TEST_CHECK_PROD_STR bool "Check product string descriptor" default n help USB Host tests that check string descriptors will check the product string descriptor of the connected device. config USB_HOST_TEST_CHECK_SERIAL_STR bool "Check serial string descriptor" default n help USB Host tests that check string descriptors will check the serial string descriptor of the connected device. config USB_HOST_TEST_OTG_DRVVBUS_ENABLE depends on IDF_TARGET_ESP32S2 || IDF_TARGET_ESP32S3 bool "Enable driving VBUS by an internal DRVVBUS signal from USB-OTG peripheral" default n help USB-OTG peripheral features a DRVVBUS signal, which controls the VBUS voltage. The DRVVBUS signal can be either internally connected to a PHY (if a PHY supports it), in such a case the PHY would be controlling the VBUS voltage by itself. Or the DRVVBUS can be handled by an external logic (a transistor switch). Our PHY does not support the DRVVBUS signal, thus we must use an external logic to control the VBUS voltage. The DRVVBUS signal is controlled via HCD_PORT_CMD_POWER_OFF and HCD_PORT_CMD_POWER_ON config USB_HOST_TEST_OTG_DRVVBUS_GPIO depends on USB_HOST_TEST_OTG_DRVVBUS_ENABLE int "Connect a GPIO to the internal DRVVBUS signal" range ENV_GPIO_RANGE_MIN ENV_GPIO_OUT_RANGE_MAX default 1 help GPIO number, that will be internally connected to the DRVVBUS signal. USB Host CI target runners feature an external power switch controlled by this GPIO, to control the VBUS voltage of USB devices during test. endmenu