From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] DDR2 driver strength and ODT on FSL 85xx
Date: Tue, 03 Aug 2010 08:32:46 +0300 [thread overview]
Message-ID: <4C57A9FE.9040400@embedded-sol.com> (raw)
Hi,
I'm working on a custom board based on FSL P1011. The board has 128MB of
soldered
DDR2 connected to a single chip select. Simulation results indicate that
better DDR2
behavior would be achieved by using half strength DDR drivers. The
driver strength
on P1011 is controlled by DDR_SDRAM_CFG[HSE] and various fields in
DDR_CDR_1.
I also need to configure DDR ODT, which is controlled by DDR_CDR_2
register.
The problem is that DDR setup code for P1020/P1011 does not configure
DDR_CDR_X
registers. I was tempted to add them to struct fsl_ddr_cfg_regs_s, and
modify
fsl_ddr_set_memctl_regs() in ddr_gen2.c to deal with them, but noticed
that on some 85XX
SoC (e.g. MPC8548), there's a single DDR_CDR register, which is not part
of DDR CCSR
space. Which means that current definition of struct ccsr_ddr in
immap_85xx.h is not
correct for these SoCs.
How would you suggest to solve my problem in a generic way ?
Thanks.
Felix.
reply other threads:[~2010-08-03 5:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C57A9FE.9040400@embedded-sol.com \
--to=felix@embedded-sol.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