Hi Abraham > > EHCI/OHCI. > > Now, I'm using ohci/ehci-platform.c > > Thats a generic ehci driver. I was interested in the specific usb > controller that uses this phy. Anyways now I know its a host only > driver :-) (snip) > Yeah. We are in the process of cleaning it up. Indeed it's normal in > the sense quite a few host only drivers use it (ehci-fsl.c, > ehci-msm.c, ehci-mv.c, ehci-tegra.c, ohci-omap.c). > > > > Now, I'm using ehci/ohci-platform. > > When I support this usb_xxx_phy(), do I need to customize these drivers ? > > You can't change ehci-platform.c because thats a generic driver. But > you have to do those modifications in your controller specific file. OK. I see. > However if two modules add themselves to the same *initcall* section, > the order in which the files are compiled determine the order in which > the modules are probed (I think this is what is happening in your > case). Yes. exactly OK, I use subsys_initcall() for my phy Best regards --- Kuninori Morimoto -- 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
