Messages in this thread | | | From | "Turquette, Mike" <> | Date | Tue, 17 Apr 2012 15:13:49 -0700 | Subject | Re: [PATCH 1/4] clk: select CLKDEV_LOOKUP for COMMON_CLK |
| |
On Mon, Apr 9, 2012 at 1:24 PM, Rob Herring <robherring2@gmail.com> wrote: > From: Rob Herring <rob.herring@calxeda.com> > > Using the common clock infrastructure without the common clkdev code makes > little sense, so select CLKDEV_LOOKUP for COMMON_CLK. > > Signed-off-by: Rob Herring <rob.herring@calxeda.com> > --- > drivers/clk/Kconfig | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig > index 165e1fe..f05a60d 100644 > --- a/drivers/clk/Kconfig > +++ b/drivers/clk/Kconfig > @@ -12,6 +12,7 @@ config HAVE_MACH_CLKDEV > config COMMON_CLK > bool > select HAVE_CLK_PREPARE > + select CLKDEV_LOOKUP > ---help--- > The common clock framework is a single definition of struct > clk, useful across many platforms, as well as an
Hi Rob,
I agree that the common clk framework is not particularly useful without clkdev. However the core code has no dependency on clkdev. Why not just select it from an arch Kconfig, or even make it a dependency based on your own platform clock data/code?
Regards, Mike
> -- > 1.7.5.4 > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |