From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix memory initialization on MPC8349ITX
Date: Tue, 24 Apr 2007 13:04:29 -0500 [thread overview]
Message-ID: <462E46AD.7090608@freescale.com> (raw)
In-Reply-To: <CF7E46FCFF66AD478BB72724345289EC27960B@twx-exch01.twacs.local>
Benedict, Michael wrote:
> Hello,
> This is my first patch submission to u-boot, so let me know if
> the format needs to be updated.
There should be a "---" underneath the signed-off-by lines, and comments about the patch
should be located *below* the "---". Patches for 83xx should be posted to u-boot-users
and emailed to Kim Phillips directly.
> Define CFG_DDR_SDRAM_CLK_CNTL for the MPC8349ITX. This allows
> ddr->sdram_clk_cntl to be properly initialized, like it was before
> commit f6eda7f80ccc13d658020268c507d7173cf2e8aa to
> cpu/mpc83xx/spd_sdram.c
You should probably update fixed_sdram() in mpc8349itx.c as well. Currently, it has this
code:
im->ddr.sdram_clk_cntl =
DDR_SDRAM_CLK_CNTL_SS_EN | DDR_SDRAM_CLK_CNTL_CLK_ADJUST_05;
That should be changed to
im->ddr.sdram_clk_cntl = CFG_DDR_SDRAM_CLK_CNTL;
I'll test this code on my ITX, however, I'm curious about one thing. Can you explain why
this patch is okay for *all* ITX boards? I remember something about your board having
problematic DDR or something. With your patch, all ITX and ITX-GP boards will set
sdram_clk_cntl to the new value when SPD is used.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-04-24 18:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 16:51 [U-Boot-Users] [PATCH] Fix memory initialization on MPC8349ITX Benedict, Michael
2007-04-24 18:04 ` Timur Tabi [this message]
2007-04-24 18:38 ` Benedict, Michael
2007-04-24 18:43 ` Timur Tabi
2007-04-24 18:50 ` Benedict, Michael
2007-04-24 18:54 ` Timur Tabi
2007-04-25 14:09 ` Kim Phillips
2007-04-25 22:22 ` Timur Tabi
2007-04-25 22:54 ` Timur Tabi
2007-04-26 13:20 ` Benedict, Michael
2007-04-26 14:33 ` Timur Tabi
2007-04-26 14:36 ` Benedict, Michael
2007-04-26 14:39 ` Timur Tabi
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=462E46AD.7090608@freescale.com \
--to=timur@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 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.