On Wed, Aug 12, 2015 at 01:05:58PM +0300, Grygorii Strashko wrote: > On 08/12/2015 01:06 AM, Michael Turquette wrote: > > Quoting Russell King - ARM Linux (2015-08-11 12:25:15) > >> > >> clk_enable/clk_disable _should_ be usable from atomic contexts. > > Thanks Russell - above is not true on -RT. What I'm saying is that it _should_ be true. You _should_ be able to call clk_enable()/clk_disable() from atomic contexts. It's been documented since forever: /** * clk_enable - inform the system when the clock source should be running. * @clk: clock source * * If the clock can not be enabled/disabled, this should return success. * * May be called from atomic contexts. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ /** * clk_disable - inform the system when the clock source is no longer required. * @clk: clock source * * Inform the system that a clock source is no longer required by * a driver and may be shut down. * * May be called from atomic contexts. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If that's not true with CCF, that's a CCF bug, not a usage bug. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
