* Tomi Valkeinen <tomi.valkeinen@xxxxxx> [120319 07:01]: > On Mon, 2012-03-19 at 15:02 +0200, Tomi Valkeinen wrote: > > > I'll see if I can make a single patch that fixes the issue. The patch > > series I mentioned earlier does lots of things, but I think just moving > > the driver registration out of the probe function should be enough to > > avoid the problem. > > Here's a patch that fixes the issue for me. Tested on OMAP4 Blaze with > omapdss both as module and built-in. I'll queue this up after testing it > a bit more. OK works for me too. > This still leaves the issue of initialization order, but I think that's > not a big issue at the moment. It doesn't happen in practice, as the > current driver framework will probe the devices at driver registration > time. I'll fix this for the next merge window. Yes that's something that needs fixing. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
