Hi Mike, On Fri, Aug 07, 2015 at 12:09:27PM -0700, Michael Turquette wrote: > All of the other kitchen sink stuff (DT binding, passing the flag back > to the framework when the clock consumer driver calls clk_put) was left > out because I do not see a real use case for it. If one can demonstrate > a real use case (and not a hypothetical one) then this patch series can > be expanded further.
I think there is a very trivial use case for passing back the reference to the framework, if during the probed, we have something like: clk = clk_get() clk_prepare_enable(clk) foo_framework_register() if foo_framework_register fails, the sensible thing to do would be to call clk_disable_unprepare. If the clock was a critical clock, you just gated it. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
signature.asc
Description: Digital signature