On 9 March 2016 at 16:24, Tomi Valkeinen <tomi.valkeinen at ti.com> wrote: > On 09/03/16 18:19, Emil Velikov wrote: >> Hi Sebastian, >> >> On 8 March 2016 at 16:39, Sebastian Reichel <sre at kernel.org> wrote: >> >>> arch/arm/boot/dts/omap3-n950-n9.dtsi | 72 +++++++++ >>> arch/arm/boot/dts/omap3-n950.dts | 71 +++++++++ >> Just a friendly reminder that updating these and one will have to keep >> the driver backwards compatible forever. >> >> Tomi, has been in the process of removing all the unneeded cruft, >> although omapdrm it is still using the custom panel, dsi and other >> code as opposed to the ones provided by DRM. As he gets to reusing >> those he might have some fun keeping things compatible. >> >> It's up-to Tomi to decide, just thought I point it out. > > I haven't looked at this series yet, but all the omap display DT > bindings have been designed to be correct, and while omapdrm will > receive lots of changes, I don't see any need to touch anything in the > DT side. > > Of course, if we will be using some existing common driver which > implements bindings in some other way, it'll cause some complexities... > I'm leaning that you want to use the existing the DRM_PANEL driver (gpu/drm/drm_panel.c). It has enough infrastructure to support 25+ 'simple' panels (gpu/drm/panel/panel-simple.c) plus 5+ more complex ones (gpu/drm/panel/).
>From a quick look the binding, they do differ although do take a look for yourself: Documentation/devicetree/bindings/display/panel/{display-timing,panel-dpi,panel-dsi-cm,simple-panel}.txt Regards, Emil