From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] HMI1001: add support for MPC5200 Rev. B processors.
Date: Thu, 13 Mar 2008 16:51:31 +0100 [thread overview]
Message-ID: <20080313155131.GD17306@game.jcrosoft.org> (raw)
In-Reply-To: <1205415198-16756-1-git-send-email-wd@denx.de>
On 14:33 Thu 13 Mar , Wolfgang Denk wrote:
> Signed-off-by: Wolfgang Denk <wd@denx.de>
> ---
> board/hmi1001/hmi1001.c | 18 ++++++++++++++++++
> 1 files changed, 18 insertions(+), 0 deletions(-)
>
> diff --git a/board/hmi1001/hmi1001.c b/board/hmi1001/hmi1001.c
> index 9fa0e74..3ecb74a 100644
> --- a/board/hmi1001/hmi1001.c
> +++ b/board/hmi1001/hmi1001.c
> @@ -147,6 +147,24 @@ long int initdram (int board_type)
>
> #endif /* CFG_RAMBOOT */
>
> + /*
> + * On MPC5200B we need to set the special configuration delay in the
> + * DDR controller. Please refer to Freescale's AN3221 "MPC5200B SDRAM
> + * Initialization and Configuration", 3.3.1 SDelay--MBAR + 0x0190:
> + *
> + * "The SDelay should be written to a value of 0x00000004. It is
> + * required to account for changes caused by normal wafer processing
> + * parameters."
> + */
> + svr = get_svr();
> + pvr = get_pvr();
> + if ((SVR_MJREV(svr) >= 2) &&
> + (PVR_MAJ(pvr) == 1) && (PVR_MIN(pvr) == 4)) {
> +
> + *(vu_long *)MPC5XXX_SDRAM_SDELAY = 0x04;
> + __asm__ volatile ("sync");
> + }
> +
> /* return dramsize + dramsize2; */
Do we need to keep it?
> return dramsize;
> }
Best Regards,
J.
next prev parent reply other threads:[~2008-03-13 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 13:33 [U-Boot-Users] [PATCH] HMI1001: add support for MPC5200 Rev. B processors Wolfgang Denk
2008-03-13 15:51 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-03-13 16:42 ` Wolfgang Denk
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=20080313155131.GD17306@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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