From: Michael Trimarchi <michael@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 2/3] sunxi: Don't change the rank in dram size detection in A33
Date: Tue, 12 Feb 2019 17:57:07 +0100 [thread overview]
Message-ID: <20190212165708.23040-2-michael@amarulasolutions.com> (raw)
In-Reply-To: <20190212165708.23040-1-michael@amarulasolutions.com>
Change the size create a glitch in the clke signal on second
bank. The glitch can generate problem in memory initialiazation
Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
---
arch/arm/mach-sunxi/dram_sun8i_a33.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm/mach-sunxi/dram_sun8i_a33.c b/arch/arm/mach-sunxi/dram_sun8i_a33.c
index 83212aaddf..d73a93a132 100644
--- a/arch/arm/mach-sunxi/dram_sun8i_a33.c
+++ b/arch/arm/mach-sunxi/dram_sun8i_a33.c
@@ -45,14 +45,12 @@ static void mctl_set_cr(struct dram_para *para)
static void auto_detect_dram_size(struct dram_para *para)
{
- u8 orig_rank = para->rank;
int rows, columns;
/* Row detect */
para->page_size = 512;
para->seq = 1;
para->rows = 16;
- para->rank = 1;
mctl_set_cr(para);
for (rows = 11 ; rows < 16 ; rows++) {
if (mctl_mem_matches(1 << (rows + 9))) /* row-column */
@@ -69,7 +67,6 @@ static void auto_detect_dram_size(struct dram_para *para)
}
para->seq = 0;
- para->rank = orig_rank;
para->rows = rows;
para->page_size = 1 << columns;
mctl_set_cr(para);
--
2.17.1
next prev parent reply other threads:[~2019-02-12 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 16:57 [U-Boot] [RFC PATCH 1/3] sunxi: Use clrsetbits_le32 instead of multiple instruction Michael Trimarchi
2019-02-12 16:57 ` Michael Trimarchi [this message]
2019-02-13 8:44 ` [U-Boot] [RFC PATCH 2/3] sunxi: Don't change the rank in dram size detection in A33 Maxime Ripard
2019-02-13 8:49 ` Michael Nazzareno Trimarchi
2019-02-13 11:10 ` Michael Nazzareno Trimarchi
2019-02-12 16:57 ` [U-Boot] [RFC PATCH 3/3] sunxi: Fix A33 memory initialization Michael Trimarchi
2019-02-13 8:45 ` Maxime Ripard
2019-02-13 8:50 ` Michael Nazzareno Trimarchi
2019-02-13 15:54 ` Maxime Ripard
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=20190212165708.23040-2-michael@amarulasolutions.com \
--to=michael@amarulasolutions.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.