Re: [PATCH] clk: Make clock framework user selectable

On Mon, Aug 15, 2016 at 03:06:10PM -0700, Stephen Boyd wrote:

On 08/11, Mark Brown wrote:

quoted

 config COMMON_CLK
-	bool
+	bool "Common Clock Framework Support"
+	depends on !HAVE_CUSTOM_CLK

Is the plan that architectures will keep selecting this when they
want to enforce common clk framework on their arch? We could move

I think that's a per-architecture thing - if the architecture doesn't
need control of clocks then there's no reason for it to force the API
on, but if the architecture is unlikely to do anything useful without
then it's a different story.

enabling this config to the defconfigs if we make of_clk_init() a
stub when this config is disabled. Interestingly arm already has
that ifdefed out so nothing fails to compile there, but not every
arch is following that design.

That's probably a good idea anyway.

Also, are there patches for all the users to select
HAVE_CUSTOM_CLK? Otherwise we can get randconfig failures when
two places define clk API functions.

They're trivial to make if you apply this.