On Tue, May 22, 2012 at 06:20:16AM +0200, Marek Vasut wrote: > Dear Shawn Guo, > > > On 22 May 2012 11:25, Marek Vasut <marex@xxxxxxx> wrote: > > > Dear Shawn Guo, > > > > > >> Apart from my comments below, we really need to know Rob and Grant's > > >> opinion on this. > > > > > > Hm ... so why don't you actually write per-board driver ? :-) That'd > > > handle every single board very well, you'd configure the GPIOs there, > > > every single additional necessary thing that has to be configured would > > > sink there too etc. > > > > I'm not completely sure about how the per-board driver looks like > > exactly. Can you have some code demonstrating it? > > Well such per-board driver would handle the board-specific init, like > configuring the hub GPIO (as Richard has to do so on mx6q) or flick some other > GPIOs, configure registers etc. > So when you say driver, you just meant a C file like imx6q-sabrelite.c containing a number of init functions to be called by mach-imx6q.c? -- Regards, Shawn -- 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
