linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Titinger <mtitinger@baylibre.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, linux-omap@vger.kernel.org,
	Marc Titinger <mtitinger+renesas@baylibre.com>,
	ahaslam@baylibre.com
Subject: Re: [PATCH v3 1/2] Trace: PM: promote event 'power_domain_target' to generic power domains.
Date: Wed, 14 Oct 2015 10:18:27 +0200	[thread overview]
Message-ID: <561E0FD3.6010809@baylibre.com> (raw)
In-Reply-To: <1842060.xHgP7up4AJ@vostro.rjw.lan>

On 14/10/2015 02:55, Rafael J. Wysocki wrote:
> On Monday, September 28, 2015 03:20:44 PM Marc Titinger wrote:
>> - change arg3 to a state name string: we got the current CPU rom the trace
>> backend already. This also prepares for multiple/named states in the power
>> domain, consistent with idle-states. states in the domain may match given
>> CPU states in this case, we will trace them by their name, and potentially
>> use arg2 as a link to their index for the cpuidle driver.
>>
>> - tested with Juno DP
>>
>> <idle>-0     [000]    42.395510: power_domain_target:  a53_pd index=0 'cluster-sleep-0'
>> <idle>-0     [000]    42.395528: cpu_idle:             state=4294967295 cpu_id=0
>> <idle>-0     [000]    42.395668: cpu_idle:             state=2 cpu_id=0
>>
>> - compiled for Omap2+
>>
>> Signed-off-by: Marc Titinger <mtitinger@baylibre.com>
>
> Hi,
>
> What's your intent regarding this series?  Do you want it to be applied
> separately, or is it going to be part of a larger series?

Hi Rafael,

v3 is a missed attempt to rebase this on the current head, but I did not 
fix v3 because thinking twice it's not that useful until Axel Haslam's 
multiple genpd states stuff is merged in. I'm finding v2 useful, shall I 
re-post v2 as v4 for clarity then ?

Thanks,
Marc.


>
> Thanks,
> Rafael
>


  reply	other threads:[~2015-10-14  8:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 13:22 [PATCH 0/2] Trace: PM: promote event 'power_domain_target' to generic power domains Marc Titinger
2015-09-25 13:22 ` [PATCH 1/2] " Marc Titinger
2015-09-25 14:05   ` Steven Rostedt
2015-09-28  8:44   ` [PATCH v2 " Marc Titinger
2015-09-28  8:44   ` [PATCH v2 2/2] arm: omap2+: PM: change trace_power_domain_target event format Marc Titinger
2015-09-28 13:20     ` [PATCH v3 1/2] Trace: PM: promote event 'power_domain_target' to generic power domains Marc Titinger
2015-09-28 13:31       ` kbuild test robot
2015-10-14  0:55       ` Rafael J. Wysocki
2015-10-14  8:18         ` Marc Titinger [this message]
2015-10-14 16:49           ` Rafael J. Wysocki
2015-09-28 13:20     ` [PATCH v3 2/2] arm: omap2+: PM: change trace_power_domain_target event format Marc Titinger
2015-09-25 13:22 ` [PATCH " Marc Titinger
2015-09-25 14:10   ` Steven Rostedt
2015-09-25 14:57     ` Marc Titinger
2015-10-12 23:33       ` Tony Lindgren
2015-10-13  7:59         ` Marc Titinger

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=561E0FD3.6010809@baylibre.com \
    --to=mtitinger@baylibre.com \
    --cc=ahaslam@baylibre.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mtitinger+renesas@baylibre.com \
    --cc=rjw@rjwysocki.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).