* Tomi Valkeinen <tomi.valkei...@ti.com> [110929 21:47]: > On Thu, 2011-09-29 at 10:52 -0700, Tony Lindgren wrote: > > > > Also, you might want to start looking into passing the configuration > > from DT instead to avoid the platform init code. Probably the > > panel configuration would be the place to start with that? > > I haven't actually looked at DT yet, but one reason I've been writing > and pushing these old omapfb cleanups is to get all omap2+ boards use > the new dss driver, and thus hopefully making DT adaptation easier as I > can (for now) ignore the old omapfb and omap1 boards regarding DT.
Right, makes sense. > But yes, I definitely need to look at DT. Is there a driver to be used > as a sample when looking at DT? At this point maybe just see what's in mainline in arch/arm/boot/dts and work your way back from there. The DT data should be pretty much just registers and stay operating system independent. So some of these things still need to be glued together by the bus/hwmod/driver probe code. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
