On Mon, 2014-03-10 at 12:23 +0000, Tomi Valkeinen wrote: > The DT describes the hardware, and there should be only one description > of it, no matter what the used SW is. I see compatible = "arm,pl111" in > the dts. PL111 is the LCD controller, right? Correct. > What will the DRM driver > use, then, Exactly the same properties, plus (hopefully) the generic display data, when (if) ready. > if the "arm,pl111" DT data is designed to work only for the > fbdev? The binding I proposed is *not* designed to work only with the fbdev driver, no. That's what I was trying to say all way long, if I failed - apologies. So let me say it again: with the exception display timings subnode, all other properties will be important for the DRM scan out driver as well. As to the display timings, being optional can be easily marked as deprecated and replaced with the proper solution. Now, if you find any other property I proposed being non generic enough (ie. fbdev-specific), I will happily discuss it. Once you get generic display bindings in place, I will gladly do all that will be required to make CLCD driver(s) use them. But I will rather drop and forget this patch completely that get dragged into another "display/video/CDF/DRM/whatever" discussion. Hope I made myself clear. Pawel -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
