From: Matteo Fortini <matteo.fortini@gmail.com>
To: barebox@lists.infradead.org
Subject: [PATCH] SAMA5D3X FIX AT91_SMC_CS offset stride
Date: Wed, 28 May 2014 19:16:43 +0200 [thread overview]
Message-ID: <CAC_9p+84LdjnZ=7zRtHYchpCDigYWKhy5H7Ed+gr0SnvPUDH+g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
As stated in section 29.19.32 of SAMA5D3 Series datasheet, to move
from CS(n) to CS(n+1) the stride is 0x14 and not 0x10.
For this reason, I was unable to use the NAND memory on my board (CS
configuration was not applied and the timings were wrong).
This patch fixes the problem.
Matteo
[-- Attachment #2: 0001-sama5d3x-fix-AT91_SMC_CS-offset-stride.patch --]
[-- Type: text/x-patch, Size: 753 bytes --]
From 6c26d7c00005cbf4470017a6d5361a346981bbe5 Mon Sep 17 00:00:00 2001
From: Matteo Fortini <matteo.fortini@gmail.com>
Date: Wed, 28 May 2014 19:00:42 +0200
Subject: [PATCH] sama5d3x: fix AT91_SMC_CS offset stride
---
arch/arm/mach-at91/sam9_smc.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-at91/sam9_smc.c b/arch/arm/mach-at91/sam9_smc.c
index a137da4..65c4558 100644
--- a/arch/arm/mach-at91/sam9_smc.c
+++ b/arch/arm/mach-at91/sam9_smc.c
@@ -16,7 +16,11 @@
#include <mach/at91sam9_smc.h>
+#ifdef CONFIG_ARCH_SAMA5D3
+#define AT91_SMC_CS(id, n) (smc_base_addr[id] + ((n) * 0x14))
+#else
#define AT91_SMC_CS(id, n) (smc_base_addr[id] + ((n) * 0x10))
+#endif
static void __iomem *smc_base_addr[2];
--
2.0.0.rc2
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-05-28 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 17:16 Matteo Fortini [this message]
2014-05-29 1:31 ` Bo Shen
2014-05-29 9:55 [PATCH] sama5d3x: fix " Matteo Fortini
2014-05-29 12:11 ` Jean-Christophe PLAGNIOL-VILLARD
2014-05-30 1:43 ` Bo Shen
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='CAC_9p+84LdjnZ=7zRtHYchpCDigYWKhy5H7Ed+gr0SnvPUDH+g@mail.gmail.com' \
--to=matteo.fortini@gmail.com \
--cc=barebox@lists.infradead.org \
/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