Santosh Shilimkar <santosh.shilimkar@xxxxxx> writes: > On 5/27/2011 4:32 AM, Kevin Hilman wrote: >> Signed-off-by: Kevin Hilman<khilman@xxxxxx> > > Do you plan to keep wroking the patch which dumps registers > before and after WFI ? No. I haven't thought through all the details yet, but I'm hoping that dropping this feature will "encourage" others to help think about it as well. ;) Ideally, I'd like to see this handled by perf/ftrace. We now have tracepoints for clock, clockdomain and powerdomain events. Maybe adding additional data for each of these tracepoints which snapshots some key registers values would be useful. Then, visualizing with tools like pytimechart or kernelshark could be done. Another option would be a new driver which adds a way to snapshot registers into a hash-table based on address (maybe triggered by the existing tracepoints.) This data could then be readable from userspace via the drivers read/write interface, and displayed with a tool that already knows about all the registers/bitfields etc. (e.g. omapconf.) I'd guess the the latter is probably prefered since all the register & bitfield knowlege is already in a tool like omapconf. > Ofcourse this patch is in your pm-debug branch. Right, I'll be dropping that branch. > For this change > Acked-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> Thanks, 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
