On Wed, Feb 05, 2014 at 03:56:37PM +0100, Michal Simek wrote: > Move of_clk_init() from clock driver to enable > options not to use zynq clock driver. > Use for example fixed clock setting. What is the use-case? Zynq w/o this driver makes no sense, IMHO. And even if you wanna fake clocks, why would this driver prevent it? Just replace all the input clocks with different ones and don't care about what this driver does?
> > Signed-off-by: Michal Simek <[email protected]> > --- > > Based on http://www.spinics.net/lists/arm-kernel/msg298287.html > series > > --- > arch/arm/mach-zynq/common.c | 1 + > drivers/clk/zynq/clkc.c | 2 -- > 2 files changed, 1 insertion(+), 2 deletions(-) > > diff --git a/arch/arm/mach-zynq/common.c b/arch/arm/mach-zynq/common.c > index 93ea19b..8df35f3 100644 > --- a/arch/arm/mach-zynq/common.c > +++ b/arch/arm/mach-zynq/common.c > @@ -68,6 +68,7 @@ static void __init zynq_timer_init(void) > zynq_early_slcr_init(); > > zynq_clock_init(); > + of_clk_init(NULL); Now you have two clock init functions... Sören -- 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/
