From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: Thomas Renninger <trenn@suse.de>,
linux-omap@vger.kernel.org, Jean Pihet-XID <j-pihet@ti.com>
Subject: RE: [PATCH] perf: add OMAP support for the new power events
Date: Wed, 26 Jan 2011 15:36:16 +0530 [thread overview]
Message-ID: <03564f8422854f071ee2c8caaa007ea3@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikJY2bf=ryXFAkJNZVU2A38wvEAmxipy8gJTow1@mail.gmail.com>
> -----Original Message-----
> From: Jean Pihet [mailto:jean.pihet@newoldbits.com]
> Sent: Wednesday, January 26, 2011 3:20 PM
> To: Santosh Shilimkar
> Cc: Thomas Renninger; linux-omap@vger.kernel.org; Jean Pihet-XID
> Subject: Re: [PATCH] perf: add OMAP support for the new power events
>
[...]
> > We need to track the actual power domain transitions as well
> > at hardware level.
> Agree
>
> > Can you please look at "pwrdm_pre_transition()" and
> > "pwrdm_post_transition()"
> > This code keep track of it using the next power state
> > and prev-power state.
> The current API only has 'trace_power_domain_target' which tracks
> the
> desired target state.
> I think we need an extra tracer 'trace_power_domain_hitstate' so
> that
> the trace parser can compare the desired ('target') and actually hit
> ('hitstate') states.
>
We use next state and previous state. 'hitstate' doesn't sound
well that's really secondary.
Do you plan to add that additional trace then ?
Regards,
Santosh
next prev parent reply other threads:[~2011-01-26 10:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 14:20 [PATCH] perf: add OMAP support for the new power events jean.pihet
2011-01-24 14:55 ` Santosh Shilimkar
2011-01-26 9:49 ` Jean Pihet
2011-01-26 10:06 ` Santosh Shilimkar [this message]
2011-02-07 16:05 ` Jean Pihet
2011-02-07 16:12 ` Santosh Shilimkar
2011-02-11 14:38 ` Are there CPU sleep residency HW counters in OMAP? Was: " Thomas Renninger
2011-02-11 15:07 ` Santosh Shilimkar
2011-02-10 21:02 ` Kevin Hilman
2011-02-18 18:14 ` Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2011-02-18 18:10 jean.pihet
2011-02-18 18:10 ` jean.pihet at newoldbits.com
2011-02-18 18:21 ` Santosh Shilimkar
2011-02-18 18:21 ` Santosh Shilimkar
2011-02-19 18:55 ` Santosh Shilimkar
2011-02-19 18:55 ` Santosh Shilimkar
2011-02-21 8:44 ` Jean Pihet
2011-02-21 8:44 ` Jean Pihet
2011-02-21 8:53 ` Santosh Shilimkar
2011-02-21 8:53 ` Santosh Shilimkar
2011-02-28 16:33 ` Jean Pihet
2011-02-28 16:33 ` Jean Pihet
2011-03-03 0:43 ` Kevin Hilman
2011-03-03 0:43 ` Kevin Hilman
2011-03-03 10:25 ` Jean Pihet
2011-03-03 10:25 ` Jean Pihet
2011-03-10 0:08 ` Kevin Hilman
2011-03-10 0:08 ` Kevin Hilman
2011-03-10 8:09 ` Jean Pihet
2011-03-10 8:09 ` Jean Pihet
2011-03-10 18:15 ` Kevin Hilman
2011-03-10 18:15 ` Kevin Hilman
2011-03-10 1:04 ` Paul Walmsley
2011-03-10 1:04 ` Paul Walmsley
2011-03-10 8:17 ` Jean Pihet
2011-03-10 8:17 ` Jean Pihet
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=03564f8422854f071ee2c8caaa007ea3@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-omap@vger.kernel.org \
--cc=trenn@suse.de \
/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.