On Fri, Mar 22, 2013 at 09:48:11AM -0600, Stephen Warren wrote: > This assumption was made long ago. I know drivers are supposed to assume > that clocks are disabled when they're probed, but historically that > wasn't always the case, so if the audio drivers assumed that, and then > did clk_enable() as the first thing, they got a warning due to the > enabling an already enabled clock and/or later attempts to disable the > clocks wouldn't actually disable them. No. clocks have always been able to be enabled multiple times. You should only get a warning if you try and disable it more times than you enabled it, because that's a violation of the API. Consider two drivers sharing the same input clock. If one driver disables the clock more times than it enables it, then it's treading on the other drivers need to have the clock enabled. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
