On 04/23/2012 06:33 AM, Arnd Bergmann wrote: > On Monday 23 April 2012, Hiroshi DOYU wrote: >> The AHB Bus conforms to the AMBA Specification (Rev 2.0) Advanced >> High-performance Bus (AHB) architecture. ... >> @@ -122,6 +123,7 @@ void __init tegra20_init_early(void) >> tegra_init_cache(0x331, 0x441); >> tegra_pmc_init(); >> tegra_powergate_init(); >> + tegra_ahb_gizmo_init(); >> } >> #endif >> #ifdef CONFIG_ARCH_TEGRA_3x_SOC >> @@ -132,5 +134,6 @@ void __init tegra30_init_early(void) >> tegra_init_cache(0x441, 0x551); >> tegra_pmc_init(); >> tegra_powergate_init(); >> + tegra_ahb_gizmo_init(); >> } >> #endif > > Does it really have to be "early", rather than an initcall? Why? I don't know whether it has to be early, but if this driver isn't going to be instantiated from device tree, I'd prefer it to be initialized by an explicit function call from the boards or common code rather than an initcall. It seems a lot easier to keep track of all the initialization by doing it explicitly. That said, it's quite possible this API couuld be called from say init_machine instead of init_early though. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
