[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140514143209.GB8612@ulmo>
Date: Wed, 14 May 2014 16:32:11 +0200
From: Thierry Reding <thierry.reding@...il.com>
To: Marcel Ziswiler <marcel@...wiler.com>
Cc: Stephen Warren <swarren@...dotorg.org>, stefan@...er.ch,
linux@....linux.org.uk, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-tegra@...r.kernel.org
Subject: Re: [PATCH 2/2] ARM: tegra: initial add of Colibri T30
On Wed, May 14, 2014 at 09:22:54AM +0200, Marcel Ziswiler wrote:
> On 05/13/2014 09:49 PM, Stephen Warren wrote:
> >On 05/13/2014 11:27 AM, stefan@...er.ch wrote:
[...]
> >>+ panel: panel {
> >>+ compatible = "edt,et057090dhu", "simple-panel";
> >
> >The panel-simple driver doesn't seem to know about that EDT panel. How
> >will it work out the display timings?
>
> Good question and me and Stefan actually even talked about that yesterday. I
> am actually using KMS right now as follows:
>
> video=HDMI-A-1:1280x720-16@60 video=LVDS-1:640x480-16@60'
>
> So the panel node is purely used to hook up the back light part right now.
>
> From our point of view for our completely generic module approach where each
> customer potentially hooks up his own display make/model it would be
> desirable to have some way of defining such timings directly through the
> device tree.
Every customer design would presumably get its own device tree file, so
they could easily follow the current conventions and update the
panel-simple driver with the proper compatible value and display timings
and then simply make the panel device node compatible with that.
Thierry
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists