All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "Titiano, Patrick" <p-titiano@ti.com>
Cc: Jean Pihet <jean.pihet@newoldbits.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH/RFC 2/4] OMAP2: PM debug: remove register dumping
Date: Tue, 31 May 2011 18:40:41 -0700	[thread overview]
Message-ID: <87sjrujply.fsf@ti.com> (raw)
In-Reply-To: <E8606C3FD412994585953171ED63A9340219136F97@dnce01.ent.ti.com> (Patrick Titiano's message of "Tue, 31 May 2011 10:24:10 +0200")

Hi Patrick,

"Titiano, Patrick" <p-titiano@ti.com> 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.


  reply	other threads:[~2011-06-01  1:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 23:02 [PATCH/RFC 0/4] OMAP: PM debug: remove register dump, misc cleanups Kevin Hilman
2011-05-26 23:02 ` [PATCH/RFC 1/4] OMAP3: PM debug: remove sleep_while_idle feature Kevin Hilman
2011-05-27  7:37   ` Jean Pihet
2011-05-27 15:26     ` Kevin Hilman
2011-05-27 16:01       ` Jean Pihet
2011-05-30  7:15   ` Santosh Shilimkar
2011-05-30  7:59     ` Jean Pihet
2011-05-26 23:02 ` [PATCH/RFC 2/4] OMAP2: PM debug: remove register dumping Kevin Hilman
2011-05-30  7:17   ` Santosh Shilimkar
2011-06-01  1:34     ` Kevin Hilman
2011-05-30  8:05   ` Jean Pihet
2011-05-31  8:24     ` Titiano, Patrick
2011-06-01  1:40       ` Kevin Hilman [this message]
2011-06-01 14:28         ` Titiano, Patrick
2011-05-26 23:02 ` [PATCH/RFC 3/4] OMAP3: " Kevin Hilman
2011-05-30  7:18   ` Santosh Shilimkar
2011-05-30  8:06     ` Jean Pihet
2011-05-26 23:02 ` [PATCH/RFC 4/4] OMAP2: PM debug: move wakeup timer into clockevent code Kevin Hilman
2011-05-27  5:18   ` Santosh Shilimkar
2011-05-30  7:21     ` Santosh Shilimkar
2011-05-30  8:08       ` Jean Pihet
2011-05-30  8:10         ` Santosh Shilimkar
2011-05-27  7:34 ` [PATCH/RFC 0/4] OMAP: PM debug: remove register dump, misc cleanups Jean Pihet
2011-05-27 15:00   ` Kevin Hilman
2011-06-13 12:28 ` Santosh Shilimkar
2011-06-16  0:33   ` Kevin Hilman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sjrujply.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=p-titiano@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.