On Thursday 14 March 2013 10:36 PM, Tony Lindgren wrote: > * Rajendra Nayak <rnayak@xxxxxx> [130314 05:44]: >> OMAP clock inits happen quite early, even before the slab is available. >> As part of the clock init, the common clock core tries to cache parent >> pointers (if not passed by the caller registering the clock) which >> fails in case of OMAP since the slab isn't initied. >> Without CONFIG_DEBUG_SLAB enabled, this just results in the common clock core >> retrying the caching attempt at some point later. >> However with CONFIG_DEBUG_SLAB enabled this results in a BUG() as reported >> in the link below by Tony.. >> http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg85932.html >> >> Fix this by passing static parent pointers to the common clock core >> while registering clocks. > > I wonder if we could easily fix this by initializing only some of the > clocks that early? We actually don't need any clocks that early (I mean even before slab init) We only need them before timer init. This isn't something specific to OMAP so I started looking at what others in drivers/clk seem to do. I found imx, spear, mvebu all do their clk inits within .init_time callbacks. tegra seems to even do it within .init_irq callback. Either one would work for us too :) > > If we had a two stage initialization we could dynamically allocate the > rest of the parent clocks without having to add all the static data. > > 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
