![]() Two U-Boot specific properties are added to support the possible USB connection of ID pin and VBUS on the board: If you want to activate the HOST driver with CONFIG_USB_DWC2 configuration, the VBUS protection needs to be implemented in you board code to protect the USB power line, avoiding to power up the VBUS when USB HOST is connected on USB OTG port, and avoiding to access to the same OTG internal peripheral registers from the two drivers. The U-Boot drivers for USB OTG internal peripheral, with the compatible st,stm32mp15-hsotg, does not have a full OTG support with USB host and USB device detection to avoid issue only the gadget driver is used in STM32 MPU boards with drivers/usb/gadget/dwc2_udc_otg.c activated by CONFIG_USB_GADGET_DWC2_ OTG the host driver drivers/usb/host/dwc2.c is not activated with CONFIG_USB_DWC2. These parameters are managed in U-Boot generic code or in STMicroelectronics board code (in line with LEDs and buttons on STM32 MPU boards) they can only be used if your board reuses the associated code.Į.g for STM32MP15x lines, in arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi, the properties are:
0 Comments
Leave a Reply. |