public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx23: Put back RAM voltage level to its original value
Date: Fri, 26 Apr 2013 13:01:26 -0300	[thread overview]
Message-ID: <1366992090-4331-1-git-send-email-festevam@gmail.com> (raw)

From: Fabio Estevam <fabio.estevam@freescale.com>

commit 5c2f444c9 (mxs: Reset the EMI block on mx23) changed the DDR voltage 
level, which causes mx23evk to fail to load a kernel.

Put back the original values, so that mx23evk can boot a kernel again.

Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
 arch/arm/cpu/arm926ejs/mxs/spl_mem_init.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/cpu/arm926ejs/mxs/spl_mem_init.c b/arch/arm/cpu/arm926ejs/mxs/spl_mem_init.c
index bc2d69c..4950490 100644
--- a/arch/arm/cpu/arm926ejs/mxs/spl_mem_init.c
+++ b/arch/arm/cpu/arm926ejs/mxs/spl_mem_init.c
@@ -234,7 +234,7 @@ static void mx23_mem_setup_vddmem(void)
 	struct mxs_power_regs *power_regs =
 		(struct mxs_power_regs *)MXS_POWER_BASE;
 
-	writel((0x10 << POWER_VDDMEMCTRL_TRG_OFFSET) |
+	writel((0x12 << POWER_VDDMEMCTRL_TRG_OFFSET) |
 		POWER_VDDMEMCTRL_ENABLE_ILIMIT |
 		POWER_VDDMEMCTRL_ENABLE_LINREG |
 		POWER_VDDMEMCTRL_PULLDOWN_ACTIVE,
@@ -242,7 +242,7 @@ static void mx23_mem_setup_vddmem(void)
 
 	early_delay(10000);
 
-	writel((0x10 << POWER_VDDMEMCTRL_TRG_OFFSET) |
+	writel((0x12 << POWER_VDDMEMCTRL_TRG_OFFSET) |
 		POWER_VDDMEMCTRL_ENABLE_LINREG,
 		&power_regs->hw_power_vddmemctrl);
 }
-- 
1.7.9.5

             reply	other threads:[~2013-04-26 16:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 16:01 Fabio Estevam [this message]
2013-04-26 16:20 ` [U-Boot] [PATCH] mx23: Put back RAM voltage level to its original value Marek Vasut
2013-04-26 17:14   ` Fabio Estevam
2013-04-26 18:21     ` Marek Vasut
2013-04-26 21:08       ` Fabio Estevam
2013-04-26 21:11         ` Marek Vasut
2013-04-26 16:24 ` Eric Bénard
2013-04-26 17:17   ` Fabio Estevam
2013-04-26 18:16     ` Marek Vasut
2013-04-26 19:42       ` Eric Bénard
2013-04-26 20:08       ` Fabio Estevam
2013-04-26 20:13         ` Otavio Salvador
2013-04-26 20:58           ` Marek Vasut
2013-04-26 23:01             ` Otavio Salvador
2013-04-26 23:33               ` Marek Vasut
2013-04-27 11:09                 ` Stefano Babic
2013-04-27 11:34                   ` Marek Vasut
2013-04-27 17:28                   ` Fabio Estevam
2013-04-27 17:53                     ` Otavio Salvador
2013-04-27 18:39                       ` Marek Vasut
2013-04-26 20:56         ` Marek Vasut
2013-04-26 21:10           ` Fabio Estevam
2013-04-26 21:14             ` Marek Vasut
2013-04-26 20:58       ` Fabio Estevam
2013-04-26 21:07         ` Marek Vasut
2013-04-26 18:14 ` Robert Nelson
2013-04-28  9:06 ` Stefano Babic
2013-04-28 23:06 ` Marek Vasut
2013-04-28 23:19   ` 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=1366992090-4331-1-git-send-email-festevam@gmail.com \
    --to=festevam@gmail.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