On Wed, 12 Aug 2015, Geert Uytterhoeven wrote: > On Tue, Aug 11, 2015 at 8:17 PM, Lee Jones <[email protected]> wrote: > >> I think that we can come up with a reasonable DT wrapper around the > >> flag. I will be ecstatic if we can agree that the meaning of the flag > >> can be tweaked just a bit to mean, "prevent this critical clock from > >> being disabled, as it was enabled out of reset or by the bootloader, > >> until a driver claims it and calls clk_prepare_enable". > > > > Easy, how about: > > > > 'prevent_this_critical_clock_from_being_disabled_as_it_was_enabled_out_of_reset_or_by_the_bootloader_until_a_driver_claims_it_and_calls_clk_prepare_enable' > > To make it less Linux-centric: > > "Prevent this critical clock from being disabled implicitly by the OS, as it > was enabled out of reset or by the bootloader, until it's explicitly managed > by a driver."
Hmm... I think you missed the giggles. :) -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
