From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: twd: Adjust localtimer frequency with cpufreqnotifiers
Date: Sat, 5 Mar 2011 13:49:00 +0530 [thread overview]
Message-ID: <eea425c066cc69c30f118fb102fff43e@mail.gmail.com> (raw)
In-Reply-To: <AANLkTims4e7o0sPxVnN0D1mNWDH7uC9q=pBQrBoad2os@mail.gmail.com>
Collin, Rob,
> -----Original Message-----
> From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-
> arm-kernel-bounces at lists.infradead.org] On Behalf Of Colin Cross
> Sent: Saturday, March 05, 2011 3:03 AM
> To: Rob Herring
> Cc: Russell King; Srinidhi KASAGAR; Harald Gustafsson; Linus
> Walleij; linux-kernel at vger.kernel.org; Rickard ANDERSSON; Varun
> Swara; Catalin Marinas; martin persson; linux-arm-
> kernel at lists.infradead.org
> Subject: Re: [PATCH] ARM: twd: Adjust localtimer frequency with
> cpufreqnotifiers
>
[...]
>
> Using a clock along with the cpufreq notifiers would simplify my
> patch
> some. Maybe we can use the traction this patch has among platforms
> that use the twd to get the necessary clocks added. Can you post a
> version of your patch that assumes the presence of a twd clock, and
> I'll work on getting the necessary clocks added and updating my
> patch on top of yours?
>
Some time back I also fixed the TWD scaling problem based on more
or less similar idea of pre-scaler and CPUFREQ notifiers.
Rob's clock idea was neat and useful to re-calibration
While doing this patch for OMAP I also found that
CPUFREQ notifiers does delays scaling timer frequency
and there is a tick deviation(3-4 ms) around 1st tick and
last tick around twd rescaling.
Another issue was not able to select higher fixed twd rate
and found fix for the same.
Regards,
Santosh
next prev parent reply other threads:[~2011-03-05 8:19 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 ` Santosh Shilimkar [this message]
2011-03-06 12:06 ` [PATCH] ARM: twd: Adjust localtimer frequency with cpufreqnotifiers 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
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=eea425c066cc69c30f118fb102fff43e@mail.gmail.com \
--to=santosh.shilimkar@ti.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).