From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: smp_twd: Reconfigure clockevents after cpufreq change
Date: Fri, 20 May 2011 23:50:45 +0200 [thread overview]
Message-ID: <BANLkTikzhC68w1AD59Vqw2vopDwu=YjOEQ@mail.gmail.com> (raw)
In-Reply-To: <1305851091-10096-1-git-send-email-ccross@android.com>
On Fri, May 20, 2011 at 2:24 AM, Colin Cross <ccross@android.com> 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>
OK Thomas can you take this in through the clock/timer
branch? Works fine for me and Colin and solves many problems
apart from making the code look neat.
Yours,
Linus Walleij
next prev parent reply other threads:[~2011-05-20 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 0:24 [PATCH v2] ARM: smp_twd: Reconfigure clockevents after cpufreq change Colin Cross
2011-05-20 21:50 ` Linus Walleij [this message]
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
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='BANLkTikzhC68w1AD59Vqw2vopDwu=YjOEQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--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).