public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] fdt: add fdt_add_display_timings(..)
Date: Sun, 12 Jan 2014 22:21:09 +0100	[thread overview]
Message-ID: <20140112222109.013d78a4@crub> (raw)
In-Reply-To: <52CD2E33.8000409@denx.de>

Hi Stefano,

On Wed, 08 Jan 2014 11:53:39 +0100
Stefano Babic <sbabic@denx.de> wrote:
...
> Agree that we have to sync u-boot and kernel, and this can be a way in
> the short term.
> 
> I am asking if this is in the long term the best way to do it. You are
> converting EDID values to fb_videomode *mode, and then again to the
> device node as required by DT.
> We have already had some talks about moving U-Boot configuration to DT,
> that is U-Boot can be also configured by a DT file (see for example
> support for Nvidia processors, they already support DT in U-Boot).
> 
> Anatolji, what do you think as best solution we have to follow for
> display setting ?

many drivers use struct fb_videomode internally and this display-timings
binding already exists in linux, so I think a function for converting
from fb_videomode to DT is useful. However we should probably extend
this current implementation of the function, e.g. rename it to
fdt_update_display_timings() and pass more arguments: node compatible
and the name of the parent node containing the display-timings node.
The code for searching the display-timings node is also needed for
other boards, so if it is in the function itself, it will simplify
the usage.

This function could look for display-timings node and create it if
it doesn't exist. Or update the existing node with new info.

Thanks,

Anatolij

  parent reply	other threads:[~2014-01-12 21:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  7:24 [U-Boot] [PATCH 1/5] edid: add function to convert edid to fb_videomode Christian Gmeiner
2014-01-08  7:24 ` [U-Boot] [PATCH 2/5] imx: mx6q_4x_mt41j128.cfg: enable ecspi3 clocks Christian Gmeiner
2014-01-08 10:44   ` Stefano Babic
2014-01-08 14:45     ` Christian Gmeiner
2014-01-09  7:07       ` Christian Gmeiner
2014-01-09 10:41         ` Stefano Babic
2014-01-08  7:24 ` [U-Boot] [PATCH 3/5] fdt: add fdt_add_display_timings(..) Christian Gmeiner
2014-01-08 10:53   ` Stefano Babic
2014-01-09  7:12     ` Christian Gmeiner
2014-01-09 10:44       ` Stefano Babic
2014-01-09 14:52         ` Eric Nelson
2014-01-09 15:06           ` Stefano Babic
2014-01-09 17:00           ` Stephen Warren
2014-01-09 17:19             ` Christian Gmeiner
2014-01-12 21:21     ` Anatolij Gustschin [this message]
2014-01-14  7:58       ` Christian Gmeiner
2014-01-16 11:44         ` Christian Gmeiner
2014-09-15 12:27           ` Christian Gmeiner
2014-01-08  7:24 ` [U-Boot] [PATCH 4/5] imx6: add ot1200 mr board Christian Gmeiner
2014-01-08 11:21   ` Stefano Babic
2014-01-08 14:53     ` Christian Gmeiner
2014-01-08  7:24 ` [U-Boot] [PATCH 5/5] imx6: make use of lldiv(..) Christian Gmeiner
2014-01-08 10:54   ` Stefano Babic
2014-01-08 14:46     ` Christian Gmeiner
2014-01-13 10:57   ` Stefano Babic
2014-01-08 10:40 ` [U-Boot] [PATCH 1/5] edid: add function to convert edid to fb_videomode Stefano Babic
2014-01-10 21:36 ` Eric Nelson
2014-01-14  0:36   ` Fabio Estevam
2014-01-14  2:55     ` Eric Nelson
2014-01-12 20:34 ` Anatolij Gustschin
2014-01-14  7:56   ` Christian Gmeiner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140112222109.013d78a4@crub \
    --to=agust@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox