Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: twd: Adjust localtimer frequency withcpufreqnotifiers
Date: Mon, 16 May 2011 16:44:06 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1105161642250.3078@ionos> (raw)
In-Reply-To: <4DD10814.1010103@ti.com>

On Mon, 16 May 2011, Santosh Shilimkar wrote:
> On 5/14/2011 9:21 PM, Thomas Gleixner wrote:
> Just for my understanding, the clockevents_reconfigure() needs to
> be called with interrupts disabled on that CPU as part of
> the CPUFREQ notifiers. I assume the right place is do it
> in POST notifier after the CPU clock and hence TWD clock is
> updated. Is that right ?

Yes.
 
> Since there is need to call this API in interrupt
> disable context, does it make sense to take care of it
> inside the API itself instead of relying on caller fn ?

Hmm, no strong opinion
 
> The arch's where the per CPU TWD's share clock, per-cpu
> clock-events should be reconfigured on all CPUs, whenever
> the parent(CPU) clock has changed using some thing like
> smp_call_function_any() etc. Is that right understanding?

Yes. If that's a common requirement we should move that to core code.
 
Thanks,

	tglx

  reply	other threads:[~2011-05-16 14:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  6:14 [PATCH] ARM: twd: Adjust localtimer frequency with cpufreq notifiers Colin Cross
2011-03-04 10:17 ` Linus Walleij
2011-03-04 10:27   ` martin persson
2011-03-04 20:11     ` Colin Cross
2011-03-04 20:31       ` Rob Herring
2011-03-04 21:33         ` Colin Cross
2011-03-05  8:19           ` [PATCH] ARM: twd: Adjust localtimer frequency with cpufreqnotifiers Santosh Shilimkar
2011-03-06 12:06             ` Linus Walleij
2011-03-06 14:20               ` [PATCH] ARM: twd: Adjust localtimer frequency withcpufreqnotifiers Santosh Shilimkar
2011-03-06 17:42                 ` Colin Cross
2011-03-06 19:02                   ` Linus Walleij
2011-05-12 15:14                     ` Linus Walleij
2011-05-13 10:02                       ` Thomas Gleixner
2011-05-13 10:59                         ` Linus Walleij
2011-05-13 21:15                           ` Russell King - ARM Linux
2011-05-13 21:22                           ` Colin Cross
2011-05-13 21:24                         ` Colin Cross
2011-05-14 15:51                           ` Thomas Gleixner
2011-05-16 11:18                             ` Santosh Shilimkar
2011-05-16 14:44                               ` Thomas Gleixner [this message]
2011-05-16 16:29                                 ` Colin Cross
2011-05-16 16:33                                   ` Thomas Gleixner
2011-05-16 16:43                                   ` Santosh Shilimkar
2011-05-16 23:08                                     ` Colin Cross

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=alpine.LFD.2.02.1105161642250.3078@ionos \
    --to=tglx@linutronix.de \
    --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