Hi Robert, On Tue, Jun 18, 2019 at 10:33 AM Robert Chiras <robert.chiras@xxxxxxx> wrote: > +Optional properties: > +- reset-gpios: a GPIO spec for the RST_B GPIO pin > +- pinctrl-0 phandle to the pin settings for the reset pin > +- width-mm: physical panel width [mm] > +- height-mm: physical panel height [mm] > +- display-timings: timings for the connected panel according to [1] Still not convinced we need the 'display-timings' property, even as an optional property. My understanding is that passing display timings in the devicetree is not encouraged. Last time you said you need to pass ''display-timings' to workaround the problem of connecting this panel to mx8m DCSS or eLCDIF. The panel timings come from the LCD manufacturer and it is agnostic to what display controller interface it is connected to. So I suggest making sure the timings passed in the driver are correct as per the vendor datasheet. If they are correct and one specific interface is not able to drive it, then probably it is a bug in this specific display controller interface or in the SoC clock driver. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
