[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <50095C6F.2020106@ti.com>
Date: Fri, 20 Jul 2012 18:56:07 +0530
From: Sekhar Nori <nsekhar@...com>
To: Linus Walleij <linus.walleij@...aro.org>
CC: Mike Turquette <mturquette@...aro.org>,
Kevin Hilman <khilman@...com>, <linux-kernel@...r.kernel.org>,
<shawn.guo@...aro.org>, <rob.herring@...xeda.com>,
<pdeschrijver@...dia.com>, <pgaikwad@...dia.com>,
<viresh.kumar@...aro.org>, <rnayak@...com>, <paul@...an.com>,
<broonie@...nsource.wolfsonmicro.com>, <tglx@...utronix.de>,
<ccross@...roid.com>, <linux-arm-kernel@...ts.infradead.org>,
"Karicheri, Muralidharan" <m-karicheri2@...com>
Subject: Re: [PATCH 2/2] [RFC] cpufreq: omap: scale regulator from clk notifier
Hi Linus,
On 7/17/2012 3:58 AM, Linus Walleij wrote:
> On Sat, Jul 14, 2012 at 2:16 AM, Mike Turquette <mturquette@...aro.org> wrote:
> '
>> This patch moves direct control of the MPU voltage regulator out of the
>> cpufreq driver .target callback and instead puts that logic into a clock
>> rate change notifier callback.
>
> That's heavy stuff.
>
> I was hoping that the first example of using clk notifiers would be
> something like mach-davinci replacing it's legacy clock framework
> with drivers/clk and then go in and change the horrid cpufreq hack
> that is currently in drivers/mmc/host/davinci_mmc.c to use a
> clock notifier instead of cpufreq.
>
> Sekhar/Kevin, any chance to have DaVinci converted to Mikes new
> clock framework? It doesn't look super-complex and would be a
> good example for others I think.
Murali (CCed) from TI is planning to work on it and should be posting
patches in 3rd/4th week of August. Once he is done, will work on
migrating the drivers to clock notifiers.
Thanks,
Sekhar
--
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