On Wed, Oct 21, 2015 at 11:50:07AM +0200, Geert Uytterhoeven wrote: > Hi Mike, Russell, > > On Tue, Oct 20, 2015 at 2:40 PM, Michael Turquette > <mturquette@xxxxxxxxxxxx> wrote: > > Why not keep the reference to the struct clk after get'ing it the first > > time? > > And store it where? Not my problem :) Users are supposed to hold on to the reference obtained via clk_get() while they're making use of the clock: in some implementations, this increments the module use count if the clock driver is a module, and may have other effects too. Dropping that while you're still requiring the clock to be enabled is unsafe: if it is provided by a module, then removing and reinserting the module may very well change the enabled state of the clock, it most certainly will disrupt the enable count. It's always been this way, right from the outset, and when I've seen people doing this bollocks, I've always pointed out that it's wrong. Generally, people will fix it once they become aware of it, so it's really that people just don't like reading and conforming to published API requirements. I think the root cause is that people just don't like reading what other people write in terms of documentation, and they prefer to go off and do their own thing, provided it works for them. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
