linux-kernel - Re: [PATCH v3 3/5] clk: introduce the common clock framework

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]

Date:	Thu, 1 Dec 2011 22:03:37 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Paul Walmsley <paul@...an.com>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	"Turquette, Mike" <mturquette@...com>,
	linus.walleij@...ricsson.com, patches@...aro.org,
	shawn.guo@...escale.com, magnus.damm@...il.com,
	linux-kernel@...r.kernel.org, amit.kucheria@...aro.org,
	richard.zhao@...aro.org, grant.likely@...retlab.ca,
	dsaxena@...aro.org, eric.miao@...aro.org, sboyd@...cinc.com,
	skannan@...cinc.com, linaro-dev@...ts.linaro.org,
	jeremy.kerr@...onical.com, linux-omap@...r.kernel.org,
	tglx@...utronix.de, linux-arm-kernel@...ts.infradead.org,
	arnd.bergmann@...aro.org
Subject: Re: [PATCH v3 3/5] clk: introduce the common clock framework

On Thu, Dec 01, 2011 at 11:30:16AM -0700, Paul Walmsley wrote:
> The intention behind the clk_{allow,block}_rate_change() proposal was to 
> allow the current user of the clock to change its rate without having to 
> call clk_{allow,block}_rate_change(), if that driver was the sole user of 
> the clock.

And how does a driver know that?
--
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/