All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
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 20:16:30 +0200	[thread overview]
Message-ID: <201304262016.31079.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5CG2n0=QnuVugZ8gEk0WnNB+jLyJcgR0wP2gXzC3BAvAw@mail.gmail.com>

Dear Fabio Estevam,

> On Fri, Apr 26, 2013 at 1:24 PM, Eric B?nard <eric@eukrea.com> wrote:
> > what are the values of these levels (previous one and new one) in mV ?
> 
> 0x10 ==> 2.5V
> 0x12 ==> 2.6V
> 
> 46v32m16

Eh? What's this code above?

> says that VDD is : 2.5V +/- 0.2V, so 2.6V is a valid supply
> voltage.
> 
> Not sure why 2.5V fails though.

http://s8.postimg.org/dn7jhntut/imx233_olinuxino_maxi_2_5_V_rising.jpg check 
this, this is as much as I got from tsvetan so far, it's the VDDMEM ramping. I 
dunno what's that weird drop before it starts going from 1V5 to 2V5, but it's 
strange at best and I don't like it. I think that's also the source of our 
problems, the DRAM suffers undervolt and quickly afterwards is configured for 
regular operation ... I'd say check mx23_mem_setup_vddmem() and inspect the 
result with a scope. I think we need some slow ramping function like 
mxs_power_set_vddx().

Best regards,
Marek Vasut

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

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 16:01 [U-Boot] [PATCH] mx23: Put back RAM voltage level to its original value Fabio Estevam
2013-04-26 16:20 ` 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 [this message]
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=201304262016.31079.marex@denx.de \
    --to=marex@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 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.