public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] iMX6 IPU configuration by EDID
Date: Tue, 17 Mar 2015 07:25:21 -0700	[thread overview]
Message-ID: <55083951.2030301@boundarydevices.com> (raw)
In-Reply-To: <5507FC48.3010302@brickedbrain.com>

Hi Luca,

On 03/17/2015 03:04 AM, Luca Ellero wrote:
> Hi all,
>
> I'm trying to configure IPU on a iMX6 based platform by reading EDID
> from the external monitor.
> 
> Everything seem to work fine except for the pixelclock. In particular my
> monitor has a standard resolution of 1280x1024 at 60 (108 MHz pixelclock).
> 
> When the function ipu_init_sync_panel (file ipu_disp.c) is called it
> correctly receive 108 MHz as pixelclock. but during the execution of
> this function it gets rounded to 130 MHz.
> 
> I can see that the function calls clk_round_rate to round the clock to
> 130 MHz but it's not clear for me how it works.
> 

It's been a while since I've looked at this, but I believe there's
a hidden fixed clock somewhere in the IPU driver.

	http://lists.denx.de/pipermail/u-boot/2014-January/thread.html#170363

> Can someone please tell me how to get the exact pixelclock I would like
> to achieve? I've carefully read the iMX6 manual but it's not very useful
> in this case.
>
> Another doubt that I have regards the field "ext_clk" of parameter
> "ipu_di_signal_cfg_t sig". In this case, is it better to set it or not?
> 

I believe this is supposed to be set for HDMI, such that the IPU
clock is derived from the HDMI PHY clock and it's best to use
the Linux driver as a guide.

Regards,


Eric

  reply	other threads:[~2015-03-17 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 10:04 [U-Boot] iMX6 IPU configuration by EDID Luca Ellero
2015-03-17 14:25 ` Eric Nelson [this message]
2015-03-18  8:26   ` Luca Ellero

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=55083951.2030301@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --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