On Tue, Jun 12, 2012 at 01:20:16PM +0200, Marek Vasut wrote: > Dear Felipe Balbi, > > > On Tue, Jun 12, 2012 at 12:53:15PM +0200, Marek Vasut wrote: > > > Dear Kishon Vijay Abraham I, > > > > > > > Patch series modifies the otg library to add support for multiple phys > > > > and to get a phy by type. This was initally developed to add support > > > > for omap5 which has both usb2 phy and usb3 phy. > > > > > > > > It also does some cleanup like renaming _transceiver with _phy and > > > > usb_set_transceiver is replaced with usb_add_phy to make it similar to > > > > other usb standard function names like usb_add_hcd. > > > > > > > > Changes from v4: > > > > * Rebased on > > > > http://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-next > > > > > > Reviewed-by: Marek Vasut <marex@xxxxxxx> > > > > > > btw. this was probably asked before, but do you think it's a good idea to > > > tell the PHYs apart by type? > > > > Can you suggest any other way ? Type is probably not scalable, that's > > for sure. If you have any other ideas, pleas share them. > > It's not scalable indeed -- ie. on mx28, there're two PHYs which are basically > the same. Though I have not a real suggestion, sorry. Yeah, on OMAP5 we use the same PHY controller (two instances of it) for USB3 and SATA signalling. So, what we need, actually, is a kernel-wide PHY layer. But that'll take time... -- balbi
Attachment:
signature.asc
Description: Digital signature
