Hi, On Thursday 28 November 2013 09:29 PM, Heikki Krogerus wrote: > Hi guys, > > PCI does not give any information about the PHY but we still need to > be able to take advantage of any possible vendor specific features, > such as custom PM operations, charger detection, ADP probing and > sensing, etc. the PHY provides. Since ULPI provides a way to do > runtime detection, I'm introducing this layer on top of Kishon's > generic phy framework. It gives us means to detect the ULPI product > and bind it to a driver without need for nasty platform/device > specific quirks in case of ULPI PHYs.
nice :-) Clearly there's a shortcoming in the current PHY framework to discover PHY's behind a pci. Thanks for attempting to solve it. But I think it needs a few modification like the ULPI device should be created by the glue (dwc3-pci?) and phy create should be done in phy driver. We should think of a better way for the controller to find the PHY (lets try and not use PHY CONSUMER or device name). Thanks Kishon -- 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
