All of lore.kernel.org
 help / color / mirror / Atom feed
From: stuartl@vrt.com.au (Stuart Longland)
To: linux-arm-kernel@lists.infradead.org
Subject: Where is DRAM initialisation done? [Resolved]
Date: Tue, 14 Oct 2014 19:24:45 +1000	[thread overview]
Message-ID: <543CEBDD.4090903@vrt.com.au> (raw)
In-Reply-To: <543C620C.3050302@vrt.com.au>

On 14/10/14 09:36, Stuart Longland wrote:
> I think I see a light at the end of the tunnel and hopefully not light
> from an oncoming train. :-)

Just a heads up? I managed to get things going.

As it turns out, I could get things to run stable by clocking the RAM at
375MHz instead of the U-Boot standard of 411MHz.  I didn't find a clean
way to do it, so I tweaked mxs_mem_init_clock in
arch/arm/cpu/arm926ejs/mxs/spl_mem_init.c with another #if:

> -#if defined(CONFIG_MX23)
> +#if defined(CONFIG_MXS_CLKCTRL_BASE)
> + const unsigned char divider = CONFIG_MXS_CLKCTRL_BASE;
> +#elif defined(CONFIG_MX23)
> /* Fractional divider for ref_emi is 33 ; 480 * 18 / 33 = 266MHz */
> const unsigned char divider = 33;
> #elif defined(CONFIG_MX28)
> /* Fractional divider for ref_emi is 21 ; 480 * 18 / 21 = 411MHz */
> const unsigned char divider = 21;
> #endif

then I could set the clock divider directly in include/configs/ts7400.h.
 The imx-bootlets code I had set that divider to 22, yielding a 392MHz
clock.  Setting it to 23 got things stable.

It may be possible to get things working properly at the normal speed
but this is beyond my skill level, so I'll leave it there.
-- 
Stuart Longland
Systems Engineer
     _ ___
\  /|_) |                           T: +61 7 3535 9619
 \/ | \ |     38b Douglas Street    F: +61 7 3535 9699
   SYSTEMS    Milton QLD 4064       http://www.vrt.com.au

      reply	other threads:[~2014-10-14  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 22:45 Where is DRAM initialisation done? Stuart Longland
2014-10-13 23:02 ` Fabio Estevam
2014-10-13 23:11   ` Fabio Estevam
2014-10-13 23:36     ` Stuart Longland
2014-10-14  9:24       ` Stuart Longland [this message]

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=543CEBDD.4090903@vrt.com.au \
    --to=stuartl@vrt.com.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.