On Fri, 2014-03-07 at 11:35 +0000, Tomi Valkeinen wrote: > > ... and this makes me try to get out of its way. In other words, I fully > > agree with you, but I don't think this applies to this particular patch, > > as I'm not even trying to represent the display pipeline. The (optional) > > Right, you are not, at the moment. My point was, if the driver is > extended later to support pipelines, or common panel/encoder drivers, > you (most likely) need to have similar bindings than the other people use. No argument here. > Note that the same DT bindings you add here should also work for the DRM > driver in the future. So, in fact, the question is extended to: will the > fbdev No, I don't think so. It's a end of line for it, I believe. From my personal point of view the main goal is to fill the last gap between DT and non-DT support on one of the Versatile Express boards - CLCD works fine when booted with ATAGs, doesn't work when booted with DT. It looks bad. > or drm driver support common panels/encoders? I would hope so, yes. VE display pipeline is quite complex (more than I would hope ;-) so to implement KMS in a proper way (with hotplugging, bells and whistles) it will have to know more than now. But it's out of scope for me. Pawel -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
