From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] i.MX28: Increase the delay after DRAM init
Date: Thu, 3 May 2012 16:39:57 +0200 [thread overview]
Message-ID: <201205031639.57627.marex@denx.de> (raw)
In-Reply-To: <m2pqal2vbw.fsf@lamuella.denx.de>
Dear Detlev Zundel,
> Hi Marek,
>
> [...]
>
> >> Can you please comment on why we are waiting and why we are waiting
> >> exactly this long? Can we maybe poll the needed time somehow?
> >
> > We need to wait for the CPU clock to stabilize.
>
> This would be a worthwhile comment in the code.
Indeed, will do
>
> > I think there is a bit for that that we can poll, indeed.
>
> And _that_ is even better ;)
I'm not doing this in this patch, I want a stable implementation here and I can
break it later ;-)
>
> > It's in my queue to revise the memory init code eventually actually,
> > because I think I can make it even faster and fix some rough edges
> > that are still there.
>
> Thanks!
> Detlev
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-05-03 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 22:14 [U-Boot] [PATCH 1/3] Revert "i.MX28: Enable additional DRAM address bits" Marek Vasut
2012-05-02 22:14 ` [U-Boot] [PATCH 2/3] M28: Scan only first 512 MB of DRAM to avoid memory wraparound Marek Vasut
2012-05-02 22:14 ` [U-Boot] [PATCH 3/3] i.MX28: Increase the delay after DRAM init Marek Vasut
2012-05-02 22:55 ` Fabio Estevam
2012-05-02 23:27 ` Marek Vasut
2012-05-03 8:12 ` Detlev Zundel
2012-05-03 13:31 ` Marek Vasut
2012-05-03 14:27 ` Detlev Zundel
2012-05-03 14:39 ` Marek Vasut [this message]
2012-05-03 15:34 ` Marek Vasut
2012-05-04 9:16 ` Detlev Zundel
2012-05-03 8:11 ` [U-Boot] [PATCH 1/3] Revert "i.MX28: Enable additional DRAM address bits" Detlev Zundel
2012-05-03 13:36 ` Marek Vasut
2012-05-03 14:30 ` Detlev Zundel
2012-05-03 14:41 ` Marek Vasut
2012-05-04 9:15 ` Detlev Zundel
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=201205031639.57627.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.