> > > > Thanks for working on this, but it is just a PHY list, not the PHY > layer > > used by PHY driver and controller driver who wants to use PHY. > > Besides, no USB Spec says there is relationship between OTG and USB PHY. > > Heikki's (including mine) aim is separate PHY from OTG, and create a > > generic PHY layer. A generic PHY layer is like below: > > > > - There is separate folder at drivers/usb/phy, which includes generic > PHY > > files and platform PHY drivers. > > - Platform PHY driver will add itself to PHY list, and implement kinds > of > > PHY utilities, like init, suspend, wakeup, charger detector, etc. > > - The PHY user (controller driver, no only otg driver) will get the PHY, > > and use it. > > Completely agree with you. But before we have the generic PHY layer, > we got to have multi-phy support. It's needed for usb3 controller in > OMAP5 where it needs usb2 phy and usb3 phy. > I see. Felipe, would you give me some suggestion that my generic PHY work should be on current tree or you think Kishon's patchset is ok, and I should be based his work when it is in your usb tree? Thanks > Thanks > Kishon -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
