From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] mpc83xx: add config options to spd_sdram
Date: Wed, 6 Apr 2011 09:37:29 -0700 [thread overview]
Message-ID: <1302107849.4586.14.camel@oslab-l1> (raw)
In-Reply-To: <4D9C21EA.3070005@matrix-vision.de>
On Wed, 2011-04-06 at 10:18 +0200, Andre Schwarz wrote:
> Kim, York,
>
> >> I have made some mods to spd_sdram.c for various reason:
> >>
> >> 1.
> >> use SPD setup also for soldered RAM.
> >> This allows DDR mounting options without U-Boot change because SPD data
> >> is written during in-circuit/boundary-scan testing.
> > not sure I understand this - board with soldered RAM can't physically
> > get the SPD data from RAM, yet SPD data were somehow acquired and
> > written into some ROM, so spd_sdram() is still needed to parse&
> > program the controller without requiring a new u-boot binary?
> SPD data is nothing more than an I2C-EEPROM soldered on each memory module
> containing the physical details of the memory devices.
> Since I already have an I2C-EEPROM on the board I can use it for SPD
> data, i.e.
> the board's memory is configured using normal detection routines.
>
> During production (exactly: board testing) the EEPROM will be programmed
> with an SPD
> table matching the soldered memory devices. This gives some flexibility
> regarding size and
> speed grades ... some devices have pretty short life-cycles.
That's right. If you have the SPD in I2C-EEPROM, you have a real SPD as
far as software concerns. Just provide the I2C address.
> >> 3.
> >> for optimized signal integrity and power consumption we need more
> >> influence on
> >> the on-die termination. Although the assumed default values are working they
> >> are far from ideal.
> > board specific things like this are perfectly acceptable, of course.
> ok.
> > however, it should not be being done by glittering old-83xx/spd_sdram
> > with an extra #ifdef for every new parameter
>
> ok - what about this :
>
> #if !defined(CONFIG_SYS_DDR_MODE_ODT_VALUE)
> #define CONFIG_SYS_DDR_MODE_ODT_VALUE 0x40
> #endif
>
> mode_odt_enable = CONFIG_SYS_DDR_MODE_ODT_VALUE;
>
>
> I really can't think of this change being a problem for anybody.
>
I would suggest to put it in fsl_ddr_board_options() in ddr.c under the
board directory. There you can override any options, including
popts->cs_local_opts[i].odt_rd_cfg
popts->cs_local_opts[i].odt_wr_cfg
popts->cpo_override
York
next prev parent reply other threads:[~2011-04-06 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 9:49 [U-Boot] [RFC] mpc83xx: add config options to spd_sdram Andre Schwarz
2011-04-05 21:52 ` Kim Phillips
2011-04-05 22:03 ` York Sun
2011-04-06 8:42 ` Andre Schwarz
2011-04-06 16:30 ` York Sun
2011-04-06 8:18 ` Andre Schwarz
2011-04-06 16:37 ` York Sun [this message]
2011-04-06 18:42 ` Schwarz, Andre
2011-04-07 20:42 ` Schwarz, Andre
2011-04-07 20:56 ` York Sun
2011-04-08 7:41 ` Andre Schwarz
2011-04-08 15:31 ` York Sun
2011-04-08 16:29 ` Andre Schwarz
2011-04-08 16:36 ` York Sun
2011-04-08 16:43 ` 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=1302107849.4586.14.camel@oslab-l1 \
--to=yorksun@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