Hi Amit, Eric, Amit Kucheria <amit.kucheria@xxxxxxxxxx> writes: > Eric, > > This looks interesting, but I'll add the linux-omap list to CC so > someone can verify if there isn't already a patch to export this. We used to have similar PM debug code in the kernel, but as the one who maintained it, I decided to remove it. This kind of thing is obviously very SoC specific, and therefore a major pain to maintain in the kernel for all the SoCs we support in linux-omap. In my view, this kind of raw register dump/analysis does not belong in the kernel, but rather in userspace tools. What we have been moving towards is using tracepoints in the clock/clockdomain/powerdomain layers to track state transitions in all of these layers. By analyzing the trace you can similarily see the state of each of the clocks and powerdomains. We currently don't have all of the low-level details (like context loss, logic & mem state, etc.) but that is not difficult to add with some new tracepoints. I removed the in-kernel register dumping in the hope that folks would start using userspace tools perf/ftrace to do the same. Kevin -- 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
