Hi Kgene, On 11/03/2011 03:09 AM, Kukjin Kim wrote: > As I said, I don't think we should control/gate the clocks with regarding > power domain.
As far as I know there is a plan to let the drivers override start/stop_device callbacks, moreover the clock control can be disabled globally by not implementing start/stop_device callbacks or per device by not adding clkdev entities to the device clock list at runtime PM core. So IMHO, there is/going to be enough flexibility. > It should be controlled by each regarding device driver and in addition, as I > know, > to handle block of clock is not recommended on EXYNOS4 now. What do you mean by this ? I couldn't find such information in any documentation. Shouldn't "clock gate block" registers be touched by boot loader and the kernel? Our boot loaders disable all clocks, and if the global clock gate is not enabled by the kernel there is no chance any multimedia device will work. Should the global clock block gate be always enabled then ? I'm afraid it is not optimal form power management POV. -- Thanks, Sylwester -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
