public inbox for u-boot@lists.denx.de
 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: Sat, 27 Apr 2013 13:34:35 +0200	[thread overview]
Message-ID: <201304271334.35435.marex@denx.de> (raw)
In-Reply-To: <517BB201.90903@denx.de>

Dear Stefano Babic,

> On 27/04/2013 01:33, Marek Vasut wrote:
> > Dear Otavio Salvador,
> 
> Hi Fabio, Otavio, Marek,
> 
> >> On Fri, Apr 26, 2013 at 5:58 PM, Marek Vasut <marex@denx.de> wrote:
> >>> Dear Otavio Salvador,
> >>> 
> >>>> On Fri, Apr 26, 2013 at 5:08 PM, Fabio Estevam <festevam@gmail.com> 
wrote:
> >>>>> On Fri, Apr 26, 2013 at 3:16 PM, Marek Vasut <marex@denx.de> wrote:
> >>>>>> 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().
> >>>>> 
> >>>>> Ok, but can we have this patch applied and do this investigation in
> >>>>> parallel?
> >>>>> 
> >>>>> At least we could have U-boot usable on mx23 again.
> >>>> 
> >>>> I also vote for it to be applied and then do this investigation in
> >>>> parallel. Even if there're still pending issues it does improve the
> >>>> current status.
> >>> 
> >>> But someone has to do this! And so far I see noone capable/willing to
> >>> do that :(
> >> 
> >> Oh really? Fabio, other people and me are doing it. We have some
> >> people helping to debug it and using their time to help testing it so
> >> it seems like a false accusation.
> > 
> > it == grabbing a scope and doing the real measurement :(
> > 
> >> So as I said, I see no reason to not get this patch in for now.
> > 
> > I am not against in per-se. I am worried noone will come up with real fix
> > when there is a "good enough plaster" put on to cover the real problem.
> 
> I agree that we have not yet found a clear cause of the behavior - but
> ler me say that is quite bound to the hardware and how voltage is
> applied to the DDR. As the patch reports to allow to boot kernel in most
> cases, I agree with Fabio to apply this - and IMHO most investigation
> should be done by the hardware developers.

Yes, I am already pestering Tsvetan to stop lazing around and do the measurement 
;-) Actually, CCed.

So far, we only have the VDDMEM graph which doesn't look nice :-(

Best regards,
Marek Vasut

  reply	other threads:[~2013-04-27 11:34 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
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 [this message]
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=201304271334.35435.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox