On Mon, 2012-07-16 at 15:34 +0530, Rajendra Nayak wrote: > On Friday 13 July 2012 07:49 PM, Tero Kristo wrote: > > This works similarly to e.g. pwrdm_for_each(). Needed by enhanced > > usecounting debug functionality that will be added to pm-debug. > > OMAP clock framework has its own debugfs entry (/debug/clock) to expose > usecounts for clocks, so does the COMMON clock framework (/debug/clk). > Maybe there isn't one which dumps usecounts for the complete tree, > instead there is one per each clock node. > > I agree having a complete dump of the clock tree usecounts can be > useful, but can we keep it in /debug/clock for now? > The reason I am saying this is because once we move from OMAP clock to > COMMON clock, something like what 'omap_clk_for_each' does will > not be possible anyway. We might have to add the support for > dumping complete tree usecounts into the COMMON clock core.
The main idea behind the dump was to allow dumping of whole clocktree status during failed suspend. It is not that useful as a debugfs feature (you can do the same with some scripts on userspace), but this is available as a side effect from the suspend dump. -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
