Hi,
We have a board based on OMAP3621 and TPS65950. The TPS works as an USB OTG interface to OMAP. Everything works well besides one point. Let's say we have the battery being charged via USB OTG port. During the charge process we need to reboot the board, the board is rebooting, the USB cable is still attached during the reboot between the board (micro USB type B) and the PC (USB type A). Our charger can work alone in non-host-controlled-mode if reset detected, so there is no need to disconnect the USB cable from PC. But when the board restarts, just before U-Boot runs I can see the message from Windows that "new hardware was discovered - OMAP3630 device" and the Windows starts looking for proper device driver. Canceling this message doesnt' helps, if the USB cable is still attached to the PC after the Linux started we encounter problems with MUSB OTG driver (gadget drivers) to work properly, the charger switches to host-controlled-mode but the charge process never starts. Only way to bring the USB OTG back to life is to disconnect the USB OTG cable from PC, reboot the board and connect USB cable after the Linux is loaded and proper USB driver initialized.
Is there some way to block the OMAP3630 device detection mechanism from USB OTG controller side? We want to keep the way of charging the battery via USB OTG connected to PC host, but without device detection mechanism from Windows side to the point when Linux will initialize proper drivers.
Best regards,
Tomasz Kaczmarek.