From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: twd: Adjust localtimer frequency withcpufreqnotifiers
Date: Sun, 6 Mar 2011 19:50:38 +0530 [thread overview]
Message-ID: <7e9fafa016bfe536ccc373fc2cc7ba61@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=KcmqmghVxhwGvv79heRU3C+TC-v2VnWSWt7bU@mail.gmail.com>
> -----Original Message-----
> From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-
> arm-kernel-bounces at lists.infradead.org] On Behalf Of Linus Walleij
> Sent: Sunday, March 06, 2011 5:37 PM
> To: Santosh Shilimkar
> Cc: Russell King; Srinidhi KASAGAR; Harald Gustafsson; Linus
> Walleij; linux-kernel at vger.kernel.org; Rickard ANDERSSON; martin
> persson; Colin Cross; Varun Swara; Catalin Marinas; linux-arm-
> kernel at lists.infradead.org
> Subject: Re: [PATCH] ARM: twd: Adjust localtimer frequency
> withcpufreqnotifiers
>
> On Sat, Mar 5, 2011 at 9:19 AM, Santosh Shilimkar
> <santosh.shilimkar@ti.com> wrote:
>
> > 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.
>
> Is this caused by ticks that have been programmed
> already (based on the previous frequency) when the scaling
> takes effect? (That's most likely I think.)
>
That's correct Linus. I noticed that Collin's patch reduces that
problem a bit. In my patch I was always leaving the scaling
to post notifier which actually aggravates the scenario.
> The latter could be fixed by simply calling
> schedule() for each CPU connected in the same core as
> the TWD at the end of twd_update_cpu_frequency(),
> couldn't it?
>
I don't think schedule will do any difference here because
it's the actual tick duration which getting changed. The
tick does happen as per the timer load value. Now it all
depends at what point time in tick window the timer scaling
happens.
> Colin what do you say?
>
> > Another issue was not able to select higher fixed twd rate
> > and found fix for the same.
>
> Can you send out the patch?
>
Sure. May be let's get all these twd scaling
patches on the list. Rob's clock patches, Collin's
notifier patch. And then I shall post the fix on
top of that.
Regards,
Santosh
next prev parent reply other threads:[~2011-03-06 14:20 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 ` Santosh Shilimkar [this message]
2011-03-06 17:42 ` [PATCH] ARM: twd: Adjust localtimer frequency withcpufreqnotifiers 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=7e9fafa016bfe536ccc373fc2cc7ba61@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).