From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: twd: Adjust localtimer frequency withcpufreqnotifiers
Date: Thu, 12 May 2011 17:14:49 +0200 [thread overview]
Message-ID: <BANLkTi=-T6P0KrsQ8+Ot_inq1JabY62LvA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikkcYw66MiJO9Bpm+De=XD2-1MFxm-CUPp6sMqL@mail.gmail.com>
2011/3/6 Linus Walleij <linus.walleij@linaro.org>:
> On Sun, Mar 6, 2011 at 6:42 PM, Colin Cross <ccross@android.com> wrote:
>
>> Is there any way
>> for a clockevent to invalidate the current event and ask for it to be
>> reprogrammed?
>
> TGLX will know for sure... Thomas?
>
> (This is inside a CPUfreq hook for a localtimer for the record.)
I discussed this briefly with TGLX at the UDS here and he's confident
we could add some nifty feature to reprogram an event. I dare not
try to guess where the code would sit or how it'd look...
Yours,
Linus Walleij
next prev parent reply other threads:[~2011-05-12 15:14 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 [this message]
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
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='BANLkTi=-T6P0KrsQ8+Ot_inq1JabY62LvA@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).