Hi Paul and Mike, It looks like we need to start putting more effort into this clock data move now, as this is starting to hinder us on several fronts. Unfortunately I still can't personally participate in this work myself as I am now allocated to some hwmod related work, but Eduardo should have plenty of time to help with this...
Anyway, Paul, I think you have been working a bit with this topic, what is the latest status with this? Do you see any areas Eduardo can help with? If you have some partially finished work also which you don't have time yourself, we can even take a look at that. Also, I would like to receive some initial comments about the approach we should take, and I added Mike here for this as you are the maintainer for the /drivers/clk. I believe we should start by moving the clock data under /drivers/clk/omap, and potentially move also some other stuff here, like CM code, clockdomain code and clockdomain data even. Do you have any opinions on this? -Tero -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
