[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTikBvHDsVEBdEYq618sPsbh=8V9L=Q@mail.gmail.com>
Date: Fri, 13 May 2011 14:22:15 -0700
From: Colin Cross <ccross@...roid.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Santosh Shilimkar <santosh.shilimkar@...com>,
Russell King <linux@....linux.org.uk>,
Srinidhi KASAGAR <srinidhi.kasagar@...ricsson.com>,
Harald Gustafsson <harald.gustafsson@...csson.com>,
linux-kernel@...r.kernel.org,
Rickard ANDERSSON <rickard.andersson@...ricsson.com>,
martin persson <martin.persson@...ricsson.com>,
Varun Swara <Varun.Swara@....com>,
Catalin Marinas <catalin.marinas@....com>,
linux-arm-kernel@...ts.infradead.org,
Jonas Ã…berg <jonas.aberg@...ricsson.com>
Subject: Re: [PATCH] ARM: twd: Adjust localtimer frequency withcpufreqnotifiers
On Fri, May 13, 2011 at 3:59 AM, Linus Walleij <linus.walleij@...aro.org> wrote:
> 2011/5/13 Thomas Gleixner <tglx@...utronix.de>:
>
>> Does the following work for you ?
>
> This patch is interesting because it uses calc_mult_shift() and the current
> localtimer driver for TWD (arch/arm/kernel/smp_twd.c) still uses hardcoded
> mult+shift.
>
> So this patch in combination with TGLX add-on in the CPUfreq path would
> eliminate the need of using the prescaler at all, which is a more appealing
> solution to me for one, since it results in less code.
>
> Colin, do you think it will work? Or was there some specific reason to use
> a dynamic prescaler instead of doing things like this?
This sounds much better than the dynamic prescaler. Using the
prescaler causes issues with accuracy and resolution that this avoids.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists