81c44c2b2c
The framebuffer layer can be a loadable module, which forces omapfb to be a module as well. However, this breaks the lcd drivers, which are linked into the omapfb driver but each have their own module_init() function. To solve this, we split out the lcd drivers into separate modules and export omapfb_register_panel, which is the only interface required between the main omapfb driver and the lcd panel drivers. We also have to introduce a new Kconfig symbol for H3, since that lcd driver has a dependency on TPS65010, which we can express better in Kconfig than Makefile syntax. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Peter Griffin <peter.griffin@linaro.org> Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com> Cc: linux-fbdev@vger.kernel.org Cc: linux-omap@vger.kernel.org Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
27 lines
819 B
Makefile
27 lines
819 B
Makefile
#
|
|
# Makefile for the OMAP1 framebuffer device driver
|
|
#
|
|
|
|
obj-$(CONFIG_FB_OMAP) += omapfb.o
|
|
|
|
objs-yy := omapfb_main.o lcdc.o
|
|
|
|
objs-y$(CONFIG_FB_OMAP_LCDC_EXTERNAL) += sossi.o
|
|
|
|
objs-y$(CONFIG_FB_OMAP_LCDC_HWA742) += hwa742.o
|
|
|
|
lcds-y$(CONFIG_MACH_AMS_DELTA) += lcd_ams_delta.o
|
|
lcds-y$(CONFIG_FB_OMAP_LCD_H3) += lcd_h3.o
|
|
lcds-y$(CONFIG_MACH_OMAP_PALMTE) += lcd_palmte.o
|
|
lcds-y$(CONFIG_MACH_OMAP_PALMTT) += lcd_palmtt.o
|
|
lcds-y$(CONFIG_MACH_OMAP_PALMZ71) += lcd_palmz71.o
|
|
lcds-$(CONFIG_ARCH_OMAP16XX)$(CONFIG_MACH_OMAP_INNOVATOR) += lcd_inn1610.o
|
|
lcds-$(CONFIG_ARCH_OMAP15XX)$(CONFIG_MACH_OMAP_INNOVATOR) += lcd_inn1510.o
|
|
lcds-y$(CONFIG_MACH_OMAP_OSK) += lcd_osk.o
|
|
|
|
lcds-y$(CONFIG_FB_OMAP_LCD_MIPID) += lcd_mipid.o
|
|
lcds-y$(CONFIG_MACH_HERALD) += lcd_htcherald.o
|
|
|
|
omapfb-objs := $(objs-yy)
|
|
|
|
obj-$(CONFIG_FB_OMAP) += $(lcds-yy)
|