* Tomi Valkeinen <tomi.valkeinen@xxxxxx> [130322 01:30]: > Hi Tony, > > As you probably know, Overo is a very basic omap board to which you can > attach different add-on modules, like LCD module. In the current overo > board file we always add multiple LCD devices, of which the user should > only use one (the one on his module). This model of allowing multiple > LCD devices on the same video bus is causing headaches in the dss land, > and I'm removing support for it. OK yes sounds like they should be all selectable, and only the selected one gets initialized. > So what we should do is add only the LCD device that you actually have > attached. With DT this will probably be handled with separate dts files, > depending on the add-on module. > > How should this be handled with board files? Is it ok to add a board > specific kernel boot argument, parsed in the board file, which tells the > add-on board? At this point I'd stay away adding any kind of custom handling to the board-*.c files as that will make the task of removing them harder. And a kernel boot argument is something we'd have to support in the future. So if something gets added, it should be a Linux generic boot argument. Some of these add on boards can be detected over i2c, but it seems as DT is the way to go in the long run in this case. > We have similar situation in some other boards also. Yeah. There's the capebus coming that might even allow hotplugging some of these add on boards eventually. How about just make PANEL_LGPHILIPS_LB035Q02 depends on !PANEL_XYZ_DPI in drivers/video/omap2/displays/Kconfig and add some comments for now? That way people can still select LB035Q02 but not for generic configurations. Regards, Tony -- 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
