From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] FSL DDR @ 83xx
Date: Fri, 12 Dec 2008 13:16:50 -0600 [thread overview]
Message-ID: <4942B8A2.4040006@freescale.com> (raw)
In-Reply-To: <4940F437.5010107@matrix-vision.de>
Andre Schwarz wrote:
> mpc83xx/spd_sdram needs some fixes to work with latest chips :
>
> 1.
> max_data_rate seems to be mishandled. Since it's twice the physical
> clock we need much higher vaues for calculating optimum caslat ... or
> use "max_bus_clock" instead. bus_clock seems to be reasonable since the
> SPD timing values refer to clock and/or clock cycle time.
>
> if (max_data_rate >= 390 && max_data_rate < 460) { /* it is DDR 400 */
>
> This is the top-level if -> DDR-333 gives max_data_rate = 666 .... and
> goes into
>
> else if (max_data_rate >= 323) { /* it is DDR 333 */
>
> Additionally the caslat reduction code should use "<=" and ">=" for the
> evaluation of clk_cycle2 and clk_cycle3. Otherwise it will only work for
> a specific memory with SPD contents.
>
> To make it short :
> DDR-II-333 will be configured with caslat = 5 @ 133MHz Controller speed
> -> It would work fine with caslat = 3.
>
> 2.
> Actually 3 bank adress bits are quite usual. This SPD values are not yet
> evaluated.
>
> 3.
> Termination schemes (150/75/50 Ohm) and driver characteristics are not
> handled at all.
> Most boards would need this or may only run stable with the most
> conservative timings.
>
>
> Does it make sense to fix these things or is the "new" DDR code the way
> to go ?
Ultimately, one way or another, at the end of the day, when all
is said and done, the old way will be removed and the new way
will prevail. You know.
So, yeah, all of these "per board" configurations will have to
be supplied in a new file like each of the 85xx and 86xx boards
have done.
HTH,
jdl
next prev parent reply other threads:[~2008-12-12 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 17:02 [U-Boot] FSL DDR @ 83xx Andre Schwarz
2008-12-08 19:50 ` Jon Loeliger
2008-12-09 18:01 ` Andre Schwarz
2008-12-09 19:04 ` Kumar Gala
2008-12-11 9:41 ` Andre Schwarz
2008-12-12 19:13 ` Jon Loeliger
2008-12-12 19:14 ` Jon Loeliger
2009-03-03 3:40 ` Jerry Van Baren
2009-03-03 9:12 ` Andre Schwarz
2008-12-11 11:06 ` Andre Schwarz
2008-12-12 19:16 ` Jon Loeliger [this message]
2008-12-08 20:01 ` Kim Phillips
2008-12-09 10:35 ` Andre Schwarz
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=4942B8A2.4040006@freescale.com \
--to=jdl@freescale.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