Re: [PATCH] clk: ti: fix linker error with !SOC_OMAP4

2017-04-20 Thread Tero Kristo
On 20/04/17 00:43, Arnd Bergmann wrote: When none of the OMAP4-generation SoCs are enabled, we run into a link error for am43xx/am43xx: drivers/clk/ti/dpll.o: In function `of_ti_am3_dpll_x2_setup': dpll.c:(.init.text+0xd8): undefined reference to `clkhwops_omap4_dpllmx' This is easily fixed by

Re: [PATCH] clk: ti: fix linker error with !SOC_OMAP4

2017-04-20 Thread Arnd Bergmann
On Thu, Apr 20, 2017 at 4:57 PM, Tero Kristo wrote: > On 20/04/17 00:43, Arnd Bergmann wrote: >> >> When none of the OMAP4-generation SoCs are enabled, we run into a link >> error for am43xx/am43xx: >> >> drivers/clk/ti/dpll.o: In function `of_ti_am3_dpll_x2_setup': >> dpll.c:(.init.text+0xd8): un

Re: [PATCH] clk: ti: fix linker error with !SOC_OMAP4

2017-04-20 Thread Tero Kristo
On 20/04/17 18:06, Arnd Bergmann wrote: On Thu, Apr 20, 2017 at 4:57 PM, Tero Kristo wrote: On 20/04/17 00:43, Arnd Bergmann wrote: When none of the OMAP4-generation SoCs are enabled, we run into a link error for am43xx/am43xx: drivers/clk/ti/dpll.o: In function `of_ti_am3_dpll_x2_setup': dp

Re: [PATCH] clk: ti: fix linker error with !SOC_OMAP4

2017-04-21 Thread Stephen Boyd
On 04/20, Tero Kristo wrote: > On 20/04/17 18:06, Arnd Bergmann wrote: > >On Thu, Apr 20, 2017 at 4:57 PM, Tero Kristo wrote: > >>On 20/04/17 00:43, Arnd Bergmann wrote: > >>> > >>>When none of the OMAP4-generation SoCs are enabled, we run into a link > >>>error for am43xx/am43xx: > >>> > >>>drive

Re: [PATCH] clk: ti: fix linker error with !SOC_OMAP4

2017-04-21 Thread Stephen Boyd
On 04/19, Arnd Bergmann wrote: > When none of the OMAP4-generation SoCs are enabled, we run into a link > error for am43xx/am43xx: > > drivers/clk/ti/dpll.o: In function `of_ti_am3_dpll_x2_setup': > dpll.c:(.init.text+0xd8): undefined reference to `clkhwops_omap4_dpllmx' > > This is easily fixed