linux-kernel - Re: [PATCH 2/2] [RFC] cpufreq: omap: scale regulator from clk notifier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkda7g2qMErwf-nebKSOW=044=YadEzEoKWM1dT=29yueeA@mail.gmail.com>
Date:	Tue, 17 Jul 2012 00:28:14 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Mike Turquette <mturquette@...aro.org>,
	"Nori, Sekhar" <nsekhar@...com>, Kevin Hilman <khilman@...com>
Cc:	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
Subject: Re: [PATCH 2/2] [RFC] cpufreq: omap: scale regulator from clk notifier

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.

Yours,
Linus Walleij
--
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/