Hi Sascha, On Mon, May 17, 2010 at 11:36:52AM +0200, Sascha Hauer wrote: > I see an increasing number of patches trying to change the > initialization sequence of the i.MX ehci controller. It's getting harder > and harder to keep track what the changes are, what other boards > and SoCs a single patch affects and whether it just reverts another > patch. > > I thought about making the initialization completely board specific and > creating a set of helper functions which the board can call if it wants > to to prevent too much code duplication. If we really need this, I'm pro adding that kind of interface, sure. However, at least for the MX51 stuff, altering the init order wasn't necessary at all eventually, and I'm not sure about other SoCs. I also didn't follow all patches in this area I fear - could you summarize which SoC wants it differently than the current code does it? Thanks, Daniel -- 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
