All of lore.kernel.org
 help / color / mirror / Atom feed
From: josh.wu@atmel.com (Josh Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: at91: Status of NAND flash access
Date: Tue, 04 Dec 2012 18:54:25 +0800	[thread overview]
Message-ID: <50BDD661.7070803@atmel.com> (raw)
In-Reply-To: <91586D499ADFD74FBCFB8425266A5DE4013765CC370A@pluto.melinkcorp.local>

Hi, Bryan

On 12/3/2012 10:39 PM, Bryan Evenson wrote:
> I have a kernel build of 3.7-rc5 that is built for the AT91SAM9G25.  The kernel has issues when it tries to read the filesystem from NAND flash.  If I change to an NFS setup then the filesystem loads.
According to your question, it is not very clear to me, so could you 
give more detail then I can help.

What type (ubi, jffs2, or others) of your filesystem is used? How do you 
flush the file system into the nand flash, by SAM-BA, or U-Boot? With or 
without pmecc?
And what ecc type (pmecc, soft, none) do you enabled in the kernel?

> I've seen some patches on this list lately related to AT91 NAND flash (specifically this thread: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/133748.html) and I believe my problems may be related to this issue.  But, I'm having trouble following the thread to find the current status.
>
> Can anyone tell me what the status is on NAND flash access for the AT91 series with the 3.7-rc5 kernel?  If this version has a known bug, is there a different suggested version I use that fixes the issue?
In 3.7-rc5, I think the atmel nand driver should work well with 
AT91SAM9G25EK board even without the patch you mentioned in above URL.

Just for PMECC, you need add following code in 
arch/arm/boot/dts/at91sam9x5cm.dtsi:
-                        nand-ecc-mode = "soft";
+                       nand-ecc-mode = "hw";
+                        atmel,has-pmecc;        /* Enable PMECC */
+                        atmel,pmecc-cap = <2>;    /* PMECC error bits*/
+                        atmel,pmecc-sector-size = <512>;  /* sector 
size for PMECC, it is not page size */

Also you can check the readme file in: 
Documentation/devicetree/bindings/mtd/atmel-nand.txt

Best Regards,
Josh Wu

>
> Thanks,
> Bryan
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2012-12-04 10:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 14:39 at91: Status of NAND flash access Bryan Evenson
2012-12-04 10:54 ` Josh Wu [this message]
2012-12-04 16:24   ` Bryan Evenson
2012-12-05  6:59     ` Josh Wu
2012-12-05 14:15       ` Bryan Evenson
2012-12-06  3:13         ` Bryan Evenson
2012-12-06 10:30           ` Josh Wu
2012-12-06 13:20             ` Bryan Evenson
2012-12-07  9:30               ` Josh Wu
2012-12-07 13:51                 ` Bryan Evenson
2012-12-07 14:47                 ` Bryan Evenson
2012-12-10 10:51                   ` Josh Wu
2012-12-11  8:46               ` Josh Wu
2012-12-11 11:24                 ` Bryan Evenson
2012-12-11 12:56                 ` Bryan Evenson
2012-12-12  2:51                   ` Josh Wu

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=50BDD661.7070803@atmel.com \
    --to=josh.wu@atmel.com \
    --cc=linux-arm-kernel@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 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.