On 22:29-20130621, Arnd Bergmann wrote: > Building OMAP5 support without this file currently results in this link error: > > arch/arm/mach-omap2/built-in.o: In function `omap54xx_voltagedomains_init': > :(.init.text+0x6b80): undefined reference to `omap446x_vdd_core_volt_data' > :(.init.text+0x6b84): undefined reference to `omap446x_vdd_mpu_volt_data' > :(.init.text+0x6b88): undefined reference to `omap446x_vdd_iva_volt_data' > > Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx> > Cc: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> > Cc: Benoit Cousson <b-cousson@xxxxxx> > Cc: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > Cc: Paul Walmsley <paul@xxxxxxxxx> > Cc: Tony Lindgren <tony@xxxxxxxxxxx> > Cc: linux-omap@xxxxxxxxxxxxxxx > > diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile > index 0520dc4..f5038f5 100644 > --- a/arch/arm/mach-omap2/Makefile > +++ b/arch/arm/mach-omap2/Makefile > @@ -77,6 +77,7 @@ ifeq ($(CONFIG_PM_OPP),y) > obj-y += opp.o > obj-$(CONFIG_ARCH_OMAP3) += opp3xxx_data.o > obj-$(CONFIG_ARCH_OMAP4) += opp4xxx_data.o > +obj-$(CONFIG_SOC_OMAP5) += opp4xxx_data.o > endif > /* * XXX Will depend on the process, validation, and binning * for the currently-running IC. Use OMAP4 data for time being. */ #ifdef CONFIG_PM_OPP omap5_voltdm_mpu.volt_data = omap446x_vdd_mpu_volt_data; omap5_voltdm_mm.volt_data = omap446x_vdd_iva_volt_data; omap5_voltdm_core.volt_data = omap446x_vdd_core_volt_data; #endif Should we just remove this instead? these are obviously wrong. -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
