linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH arm 1/1] arm: Use _rcuidle tracepoint to allow use from idle
Date: Tue, 26 Apr 2016 12:41:19 -0700	[thread overview]
Message-ID: <20160426194119.GQ5995@atomide.com> (raw)
In-Reply-To: <20160426151725.657ae70c@gandalf.local.home>

* Steven Rostedt <rostedt@goodmis.org> [160426 12:18]:
> Time to play "Whack-a-Mole"(TM)

:)

> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
> diff --git a/arch/arm/mach-omap2/powerdomain.c b/arch/arm/mach-omap2/powerdomain.c
> index 78af6d8cf2e2..12b66b5bcc55 100644
> --- a/arch/arm/mach-omap2/powerdomain.c
> +++ b/arch/arm/mach-omap2/powerdomain.c
> @@ -523,8 +523,8 @@ int pwrdm_set_next_pwrst(struct powerdomain *pwrdm, u8 pwrst)
>  
>  	if (arch_pwrdm && arch_pwrdm->pwrdm_set_next_pwrst) {
>  		/* Trace the pwrdm desired target state */
> -		trace_power_domain_target(pwrdm->name, pwrst,
> -					  smp_processor_id());
> +		trace_power_domain_target_rcuidle(pwrdm->name, pwrst,
> +						  smp_processor_id());
>  		/* Program the pwrdm desired target state */
>  		ret = arch_pwrdm->pwrdm_set_next_pwrst(pwrdm, pwrst);
>  	}

That part is already there with "arm: Use _rcuidle tracepoint to allow
use from idle" which I did not have applied.

Regards,

Tony

  reply	other threads:[~2016-04-26 19:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 20:48 [PATCH arm 1/1] arm: Use _rcuidle tracepoint to allow use from idle Paul E. McKenney
2016-04-26 15:00 ` Tony Lindgren
2016-04-26 17:52   ` Paul E. McKenney
2016-04-26 18:29     ` Tony Lindgren
2016-04-26 19:07       ` Paul E. McKenney
2016-04-26 19:39         ` Tony Lindgren
2016-04-26 19:44           ` Steven Rostedt
2016-04-26 19:51             ` Paul E. McKenney
2016-04-26 19:52               ` Steven Rostedt
2016-04-26 20:06                 ` Paul E. McKenney
2016-04-26 19:51             ` Tony Lindgren
2016-04-26 20:06               ` Paul E. McKenney
2016-04-26 20:11                 ` Paul E. McKenney
2016-04-26 20:25                   ` Tony Lindgren
2016-04-26 20:41                     ` Paul E. McKenney
2016-04-26 20:46                       ` Tony Lindgren
2016-04-26 20:52                         ` Steven Rostedt
2016-04-26 21:08                           ` Paul E. McKenney
2016-04-26 21:04                         ` Paul E. McKenney
2016-04-26 21:12                           ` Tony Lindgren
2016-04-26 21:26                             ` Paul E. McKenney
2016-04-26 21:36                               ` Tony Lindgren
2016-04-26 20:16                 ` Steven Rostedt
2016-04-26 20:36                   ` Paul E. McKenney
2016-04-26 19:47           ` Paul E. McKenney
2016-04-26 19:17       ` Steven Rostedt
2016-04-26 19:41         ` Tony Lindgren [this message]
2016-04-26 19:42         ` Paul E. McKenney
2016-04-26 19:49           ` Steven Rostedt

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=20160426194119.GQ5995@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).