Matthieu CASTET <matthieu.castet@xxxxxxxxxx> writes: [three time's the charm; sorry for spam] > Note that some chipidea version need special callback for phy init or errata > workaround. It can be done similarly to how it's currently done in ehci-mv, I guess. I'm not sure which particular workaround you are referring to, though. > In the current version, this is done in platform driver (ehci-fsl.c, > ehci-tegra.c, ...). Are these two even chipideas? They don't look like they are from the register definitions. > I don't know you do you plan to manage them ? My idea is that if we need workarounds in the controller code for certain versions of the controller, we can do that based on the chipidea version that we can determine at run time and/or platform supplied information. This, of course, has to be part of the hdrc driver. If there is any platform specific phy code though, it has to be managed by usb_phy layer. I'm not sure if I answered your question, but please elaborate if there's anything that I'm missing. Regards, -- Alex -- 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
