public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i.MX28: Add delay after CPU bypass is cleared
Date: Sun, 06 May 2012 18:38:45 +0200	[thread overview]
Message-ID: <4FA6A915.8060809@denx.de> (raw)
In-Reply-To: <1336131170-7621-1-git-send-email-marex@denx.de>

On 04/05/2012 13:32, Marek Vasut wrote:
> This solves issues when larger amount of DRAM is used, like 256MB.
> Behave the same in case of CPU bypass as we do in case of EMI
> bypass, but wait 15 ms. We need to wait until the clock domain
> stabilizes.
> 
> This issue seemed to have been caused by not waiting after frobbing
> with the CPU bypass, it was unrelated to memory, but had a direct
> impact, causing trouble. This was yet another X-File of the
> imx-bootlets, sigh. The conclusion is, trying a semi-random delay
> (there is delay after the EMI bypass change), the issue is fixed.
> 
> Another possible explanation is that we do not do the "simple memory
> test" FSL does in their imx-bootlets (1000 R/W cycles to/from piece of
> the memory, while also outputing something on the serial port). This
> might have caused the similar delay in the imx-bootlets and therefore
> they didn't need to add this explicitly.
> 
> For now, this seems good fix enough, but to me, whole that memory
> init code in imx-bootlets is completely flunked and it'd need deeper
> investigation.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Wolfgang Denk <wd@denx.de>
> Cc: Detlev Zundel <dzu@denx.de>
> Cc: Stefano Babic <sbabic@denx.de>
> Cc: Fabio Estevam <festevam@gmail.com>
> ---
>  arch/arm/cpu/arm926ejs/mx28/spl_mem_init.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> V2: Change the description, this issue seemed to have been caused by not
>     waiting after frobbing with the CPU bypass, it was unrelated to memory,
>     but had a direct impact, causing trouble. This was yet another X-File
>     of the imx-bootlets, sigh.
> V3: Add more conspiracy theories into the commit message.
> 
> diff --git a/arch/arm/cpu/arm926ejs/mx28/spl_mem_init.c b/arch/arm/cpu/arm926ejs/mx28/spl_mem_init.c
> index 0d13537..9fa5d29 100644
> --- a/arch/arm/cpu/arm926ejs/mx28/spl_mem_init.c
> +++ b/arch/arm/cpu/arm926ejs/mx28/spl_mem_init.c
> @@ -149,6 +149,8 @@ void mx28_mem_setup_cpu_and_hbus(void)
>  	/* Disable CPU bypass */
>  	writel(CLKCTRL_CLKSEQ_BYPASS_CPU,
>  		&clkctrl_regs->hw_clkctrl_clkseq_clr);
> +
> +	early_delay(15000);
>  }
>  

It is fine with me

Acked-by: Stefano Babic <sbabic@denx.de>

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

  reply	other threads:[~2012-05-06 16:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 15:47 [U-Boot] [PATCH 1/4 V2] Revert "i.MX28: Enable additional DRAM address bits" Marek Vasut
2012-05-03 15:47 ` [U-Boot] [PATCH 2/4 RESEND] M28: Scan only first 512 MB of DRAM to avoid memory wraparound Marek Vasut
2012-05-03 15:47 ` [U-Boot] [PATCH 3/4 V2] i.MX28: Add delay after CPU bypass is cleared Marek Vasut
2012-05-04  9:20   ` Detlev Zundel
2012-05-04 11:13     ` Marek Vasut
2012-05-04 11:32   ` [U-Boot] [PATCH] " Marek Vasut
2012-05-06 16:38     ` Stefano Babic [this message]
2012-05-06 16:39       ` Marek Vasut
2012-05-07  9:49       ` Detlev Zundel
2012-05-06 16:28   ` [U-Boot] [PATCH 3/4 V2] " Stefano Babic
2012-05-06 16:30     ` Marek Vasut
2012-05-03 15:47 ` [U-Boot] [PATCH 4/4] M28: Enable FDT support Marek Vasut
2012-05-06 15:53   ` Stefano Babic
2012-05-06 16:12     ` Marek Vasut
2012-05-06 16:18       ` Stefano Babic
2012-05-06 16:41         ` Marek Vasut

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=4FA6A915.8060809@denx.de \
    --to=sbabic@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