[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5AjsjW=F7_8yS03uBtq0qKMmmNYUn-5Z+KGXOnm4up2RQ@mail.gmail.com>
Date: Fri, 23 Jan 2015 12:44:21 -0200
From: Fabio Estevam <festevam@...il.com>
To: Philipp Zabel <p.zabel@...gutronix.de>
Cc: Liu Ying <Ying.Liu@...escale.com>,
Fabio Estevam <fabio.estevam@...escale.com>,
"linux-fbdev@...r.kernel.org" <linux-fbdev@...r.kernel.org>,
Steve Longerbeam <steve_longerbeam@...tor.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
DRI mailing list <dri-devel@...ts.freedesktop.org>,
Denis Carikli <denis@...rea.com>,
Tomi Valkeinen <tomi.valkeinen@...com>,
Steve Longerbeam <slongerbeam@...il.com>,
Russell King <rmk+kernel@....linux.org.uk>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>
Subject: Re: [PATCH v2 0/7] imx-drm: ipuv3-crtc: Implement mode_fixup
Hi Philipp,
On Fri, Jan 23, 2015 at 8:50 AM, Philipp Zabel <p.zabel@...gutronix.de> wrote:
> What are this panel timings? The adjustment should increase the vertical
> back porch by up to two lines (so it is at least two lines), reducing
> the front porch or vsync length by the same amount. Does this panel use
> the HSYNC/VSYNC signals embedded in the LVDS stream?
The panel on this board is a Hannstar HSD100PXN1. The timings we use
are described in imx6qdl-sabresd.dtsi:
display-timings {
native-mode = <&timing0>;
timing0: hsd100pxn1 {
clock-frequency = <65000000>;
hactive = <1024>;
vactive = <768>;
hback-porch = <220>;
hfront-porch = <40>;
vback-porch = <21>;
vfront-porch = <7>;
hsync-len = <60>;
vsync-len = <10>;
};
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists