mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Colin Cross <ccross@android.com>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Russell King <linux@arm.linux.org.uk>,
	Rob Herring <robherring2@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: smp_twd: Reconfigure clockevents after cpufreq change
Date: Mon, 23 May 2011 12:20:46 +0530	[thread overview]
Message-ID: <4DDA03C6.6050806@ti.com> (raw)
In-Reply-To: <BANLkTikyGFVKTst1xJTGzHuwY_2GoG6NOw@mail.gmail.com>

On 5/23/2011 10:48 AM, Colin Cross wrote:
> On Fri, May 20, 2011 at 11:29 PM, Santosh Shilimkar
> <santosh.shilimkar@ti.com>  wrote:
>> On 5/20/2011 5:54 AM, Colin Cross wrote:
>>>
>>> The localtimer's clock changes with the cpu clock.  After a
>>> cpufreq transition, update the clockevent's frequency and
>>> reprogram the next clock event.
>>>
>>> Adds a clock called "smp_twd" that is used to determine the
>>> twd frequency, which can also be used at init time to
>>> avoid calibrating the twd frequency.
>>>
>>> Clock changes are based on Rob Herring's work.
>>>
>>> Change-Id: I413b5cd07fb2b79bc9fad8b4bf257332d1da7bcd
>>> Signed-off-by: Colin Cross<ccross@android.com>
>>> Cc: Thomas Gleixner<tglx@linutronix.de>
>>> Cc: Russell King<linux@arm.linux.org.uk>
>>> Cc: Santosh Shilimkar<santosh.shilimkar@ti.com>
>>> Cc: Rob Herring<robherring2@gmail.com>
>>> Tested-by: Linus Walleij<linus.walleij@linaro.org>
>>> ---
>>
>> Acked-by: Santosh Shilimkar<santosh.shilimkar@ti.com>
>>
>> What about the clock-node patches?
>> Do you want those to get merged via sub-arch tree's once this
>> patch + Thomas's new API gets merged ?
>
> The clock-node patches can be merged independently - twd scaling just
> won't work until they are both merged.
Yep. That should be ok.

Regards
Santosh

  reply	other threads:[~2011-05-23  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20  0:24 Colin Cross
2011-05-20 21:50 ` Linus Walleij
2011-05-21  3:33 ` Rob Herring
2011-05-21  6:29 ` Santosh Shilimkar
2011-05-23  5:18   ` Colin Cross
2011-05-23  6:50     ` Santosh Shilimkar [this message]
2011-05-30 12:41 ` Linus Walleij

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=4DDA03C6.6050806@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=ccross@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=robherring2@gmail.com \
    --cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome