On Tue, Nov 29, 2011 at 7:47 PM, Felipe Balbi <balbi@xxxxxx> wrote: >> >> Balbi, I can also give some help for this. >> Freescale i.mx51 bbg platform has two phys at board, one is on-chip >> UTMI phy for OTG controller, the other is ULPI phy for HOST 1 >> controller. I can post a patch using refined heikki's phy utility >> file, related phy drivers, and i.mx host driver ehci-mxc.c. Then we >> can more clearly how separated phy struct works (split from otg), phy >> driver works and how multiple PHYs works, and refine a good PHY >> framework. Do you think so? > > it would be nice to see, but as of today the host stack doesn't even > know about the PHYs, how do you plan to add that ? PHYs have, until now, > only been used by DRD/OTG and peripheral-only devices. The standard *hci > hosts never used them. Anyway, please post your patches and we can start > playing with that side too. > The current mailine Freescale i.MX usb driver do not have otg driver, but it also needs to config phy. Some phy utilities are at platform init and others are at otg/ulpi.c, you can refer ehci-mxc.c for detail. Freescale i.MX usb design (some are still not mainline) are not the same with others, like msm, which otg file is must. User can only choose host/ehci-mxc or gadget/udc-mxc if they only want host or device function. OTG file (otg/otg-mxc.c) is only be compiled when users want OTG functon. Since current otg structure combine otg operation with phy's, It's a little diffcult for i.mx driver plays at mainline code, we only add phy's code at other places since we don't need otg driver sometimes. So, split phy from otg structure, and implement phy's framework will at least benefit for non-otg design. > Put Kishon in Cc too for those PHY-related patches as he has been > playing with that lately. > > -- > balbi -- BR, Peter Chen -- 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
