> > > > In my mind, the system without OTG but using struct usb_phy can still > > track their states. > > > > One thing I am always puzzled of current code is the OTG should be no > > relationship with USB PHY. > > The system without OTG but has USB device or host only function should > > still own USB PHY. > > you don't need to tell me that. We're in the process of redesigning the > PHY and OTG apis exactly for that. This is basically legacy from the > original PHY patch (back from 2.6.18 or something) which added PHY > support considering only OTG systems. > > At that time we only had these plug&play PHYs and likely no standard > host controller on an embedded system. > > Anyway, it will take some time to finish converting everything, help's > welcome though. >
OK, glad to hear that. My RFC and questions are all for eliminating the relationship between USB PHY and USB OTG, and find some good ways to convert everything. > -- > balbi -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
