From: giometti@enneenne.com (Rodolfo Giometti)
To: linux-arm-kernel@lists.infradead.org
Subject: NAND support for Armada 370
Date: Fri, 3 Jan 2014 16:32:50 +0100 [thread overview]
Message-ID: <20140103153249.GR10251@enneenne.com> (raw)
In-Reply-To: <20140103145336.GA9618@localhost>
On Fri, Jan 03, 2014 at 11:53:37AM -0300, Ezequiel Garcia wrote:
> > pxa3xx-nand f10d0000.nand: This platform can't do DMA on this device
> > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron MT29F1G08ABADAWP)
> > NAND device: 128MiB, SLC, page size: 2048, OOB size: 64
>
> Great! Your NAND is now detected...
>
> > pxa3xx-nand f10d0000.nand: ECC strength 4 at page size 2048 is not supported
> > pxa3xx-nand f10d0000.nand: failed to scan nand at cs 0
> >
> > So I suppose I should modify function pxa_ecc_init() in file
> > drivers/mtd/nand/pxa3xx_nand.c in order to support my NAND chip, is
> > that right? Have you any advice for me about it? :)
> >
>
> Can you modify the above message so the ECC step size is also printed?
Here my modification:
diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand/pxa3xx_nand.c
index 31aae53..3e4519f 100644
--- a/drivers/mtd/nand/pxa3xx_nand.c
+++ b/drivers/mtd/nand/pxa3xx_nand.c
@@ -1498,6 +1508,8 @@ KEEP_CONFIG:
ecc_strength = chip->ecc_strength_ds;
ecc_step = chip->ecc_step_ds;
+ dev_info(&info->pdev->dev, "ECC strength %d, ECC step size %d\n",
+ ecc_strength, ecc_step);
/* Set default ECC strength requirements on non-ONFI devices */
if (ecc_strength < 1 && ecc_step < 1) {
and the corresponding output:
pxa3xx-nand f10d0000.nand: ECC strength 4, ECC step size 512
> I'll help you prepare a suitable fix to support your NAND.
Great. Thanks! :-)
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti at enneenne.com
Linux Device Driver giometti at linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it
next prev parent reply other threads:[~2014-01-03 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 12:44 NAND support for Armada 370 Rodolfo Giometti
2014-01-02 13:42 ` Thomas Petazzoni
2014-01-02 13:50 ` Rodolfo Giometti
2014-01-03 11:29 ` Rodolfo Giometti
2014-01-03 14:53 ` Ezequiel Garcia
2014-01-03 15:32 ` Rodolfo Giometti [this message]
2014-01-06 15:34 ` Rodolfo Giometti
2014-01-08 23:36 ` Ezequiel Garcia
2014-01-08 23:36 ` Ezequiel Garcia
2014-01-09 16:33 ` Rodolfo Giometti
2014-01-09 16:33 ` Rodolfo Giometti
2014-01-13 11:10 ` Ezequiel Garcia
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=20140103153249.GR10251@enneenne.com \
--to=giometti@enneenne.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.