Hi Patrick, "Titiano, Patrick" <p-titiano@xxxxxx> writes: [...] >> >> OK for this change. Is it the intention to use the omapconf tool as >> the replacement for the regs dump code? > > Sorry but omapconf is run from userspace, it cannot be used to dump > PRCM registers right before and after MPU WFI. > Right, taking register snapshots is currently beyond the scope of omapconf. However, as I suggested earlier in this thread, if we had a new driver with read/write interface where register snapshots are saved, I imagine adopting omapconf to read from such an interface for dumping register snapshots would be relatively easy, right? Kevin [1] again, I haven't really thought much about this, but something like; write an address to /dev/foo, then reading 'len' bytes from /dev/foo would give back the snapshot data (if any) starting from that address. -- 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
