On Tue, 2010-08-24 at 15:16 -0700, Kevin Hilman wrote: > Thara Gopinath <thara@xxxxxx> writes: > > > This patch changes the pm_db_init from arch initcall to a postcore > > initcall. With arch initcall, it is impossible for pm driver that > > gets initialized prior to this driver to use one of the > > pm debug fs entries during its init. Making it a postcore initcall > > ensures that this drver gets initialized early on before any pm > > drivers. > > Instead of tinkering with initcall ordering, how about calling the pm > debug init from pm.c ignore this comment, pm.c is a device_initcall, so wont solve your problem. But I'd still like to know what PM drivers are being initialized so early they need this to be a postcore_initcall. Kevin -- 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
