Hi, On Mon, 2011-01-03 at 18:21 +0530, ext Guruswamy Senthilvadivu wrote: > From: Senthilvadivu Guruswamy <svadivu@xxxxxx> > > Hwmod adaptation design requires each of the DSS HW IP to be a platform driver. > Platform driver of dsshw has to be registered before of dispc, rfbi, dsi1, > venc and omapdisplay driver should be after all the HW IPs. Sequence it with > arch_initcall and device_initcall_sync. Do you know if there some extra meaning for the _sync initcalls? The name would imply something else that just init ordering. I don't like using multiple initcall levels in the same driver. It's already quite complicated with omapdss, omapfb and the panel drivers. What were the dependencies here? Could we have just one initcall which would do the registration of platform drivers in the correct order? Does this even work if the DSS is compiled as a module? I have the recollection that a module can only have one initcall, and in this case omapdss would have many. Tomi -- 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
