Hi, On Wed, Mar 14, 2018 at 10:50:12AM +0200, Felipe Balbi wrote: > >>> - Support to replace pip3 clock going to DWC3 with utmi clock > >>> for hardware configuration where SSPHY is not used with DWC3. > >> Is that SW configurable? Really? In any case seems like this and SESSVLD > >> valid should be handled using Hans' and Heikki's mux support. > > > > Yes, with this we can use dwc3 without using SSPHY. Please point me to > > those patches. There are only bunch of register writes in glue wrapper to > > achieve the same. > > https://www.spinics.net/lists/linux-usb/msg160868.html I'm not sure if that series is usable in this case. Though we do control the VBUSVLD pin on DWC3 in the driver for the "Intel USB mux" Hans is introducing, the framework for the USB role switches does not provide any support for it. The Intel USB mux driver simply enables VBUSVLD when device mode is selected, and disables it if host mode is selected, and when the selection is cleared (disconnection). Br, -- heikki -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
