From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
To: linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Tony Lindgren <tony@atomide.com>
Cc: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>,
Sven Krauss <sven.krauss@web.de>
Subject: [PATCH] mtd: omap2-nand: avoid unaligned DMA accesses, fall back on prefetch method
Date: Thu, 20 Sep 2012 17:44:10 +0200 [thread overview]
Message-ID: <1348155850-26174-1-git-send-email-arnout@mind.be> (raw)
From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
The buffers given to the read_buf and write_buf methods are not
necessarily u32-aligned, while the DMA engine is configured with
32-bit accesses. As a consequence, the DMA engine gives an error
which appears in the log as follows:
DMA misaligned error with device 4
After this, no accesses to the NAND are possible anymore because the
access never completes. This usually means the system hangs if the
rootfs is in NAND.
To avoid this, use the prefetch method if the buffer is not aligned.
It's difficult to reproduce the error, because the buffers are
aligned most of the time.
This bug and a patch was originally reported by Sven Krauss in
http://article.gmane.org/gmane.linux.drivers.mtd/34548
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Cc: Sven Krauss <sven.krauss@web.de>
---
Perhaps a better method is to fetch the first few unaligned bytes
with the prefetch method, and then continue with DMA. However,
since it's hard to force an unaligned buffer, it's also hard to
test that this method works.
---
drivers/mtd/nand/omap2.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index c719b86..a313e83 100644
--- a/drivers/mtd/nand/omap2.c
+++ b/drivers/mtd/nand/omap2.c
@@ -441,7 +441,7 @@ out_copy:
*/
static void omap_read_buf_dma_pref(struct mtd_info *mtd, u_char *buf, int len)
{
- if (len <= mtd->oobsize)
+ if (len <= mtd->oobsize || !IS_ALIGNED((unsigned long)buf, 4))
omap_read_buf_pref(mtd, buf, len);
else
/* start transfer in DMA mode */
@@ -457,7 +457,7 @@ static void omap_read_buf_dma_pref(struct mtd_info *mtd, u_char *buf, int len)
static void omap_write_buf_dma_pref(struct mtd_info *mtd,
const u_char *buf, int len)
{
- if (len <= mtd->oobsize)
+ if (len <= mtd->oobsize || !IS_ALIGNED((unsigned long)buf, 4))
omap_write_buf_pref(mtd, buf, len);
else
/* start transfer in DMA mode */
--
1.7.10.4
next reply other threads:[~2012-09-20 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 15:44 Arnout Vandecappelle (Essensium/Mind) [this message]
2012-09-28 3:35 ` [PATCH] mtd: omap2-nand: avoid unaligned DMA accesses, fall back on prefetch method Artem Bityutskiy
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=1348155850-26174-1-git-send-email-arnout@mind.be \
--to=arnout@mind.be \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sven.krauss@web.de \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).