On 11/13/2013 05:23 AM, Mark Brown wrote: > On Tue, Nov 12, 2013 at 11:20:44AM -0700, Stephen Warren wrote: > >> The only issue you may have to watch out for is: When is >> regulator_init() called (i.e. when does core_initcall happen) >> relative to when driver probe()s can be called? If it's earlier, >> then core_initcall is early enough I suspect. > > What I said was to set this up when we hand the DT over to the DT > code to be parsed so that we don't need to worry about any gaps > like that, it seems like a more direct solution than worrying about > initcall ordering.
I guess this means putting the call to regulator_has_full_constraints() somewhere inside early_init_dt_scan(), unflatten_device_tree(), or just perhaps inside of_platform_populate() (all in drivers/of/*.c). It seems slightly odd to tightly link the drivers/of and drivers/regulator code like that, but I guess with the appropriate ifdefs it'll work out OK. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
