From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Richard Weinberger <richard@nod.at>,
Miquel Raynal <miquel.raynal@bootlin.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Marek Vasut <marek.vasut@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
"Bean Huo" <beanhuo@micron.com>
Subject: Re: [2/3] mtd: rawnand: micron: Disable ECC earlier in the read path
Date: Mon, 16 Jul 2018 18:10:57 +0200 [thread overview]
Message-ID: <20180716181057.65d78303@bbrezillon> (raw)
In-Reply-To: <a01b89d899504e8596da9e416d22b1f7@svr-chch-ex1.atlnz.lc>
On Mon, 16 Jul 2018 09:00:59 +0000
Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
> Hi Boris,
>
> On 04/07/18 00:20, Boris Brezillon wrote:
> > We are about to support extracting the real number of bitflips for
> > 4-bits ECC when WRITE_RECOMMEND is returned. This requires re-reading
> > the page in raw mode to compare it to the corrected version, and this
> > logic will be placed in micron_nand_on_die_ecc_status_4().
> >
> > Moving the micron_nand_on_die_ecc_setup() will allow us to disable
> > ECC only once.
> >
> > As a result, we have to rework the exit path and add an error path
> > where the ECC is disabled.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
>
> As I said on the other thread this appears to cause a problem for me on
> the MT29F1G08ABAFAWP-ITE setup I have. I notice we're not able to find
> the BBT, not sure if that is symptom or cause. If I revert this I can
> successfully mount and access data on the chip.
>
> Here's some output from dmesg:
>
> nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xd1
> nand: Micron MT29F1G08ABAGAWP
> nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
> nand: timing mode 5 not acknowledged by the NAND chip
> Bad block table not found for chip 0
> Bad block table not found for chip 0
> Scanning device for bad blocks
> random: fast init done
> Bad block table written to 0x000007fe0000, version 0x01
> Bad block table written to 0x000007fc0000, version 0x01
> 3 fixed-partitions partitions found on MTD device pxa3xx_nand-0
> Creating 3 MTD partitions on "pxa3xx_nand-0":
> 0x000000000000-0x000007000000 : "user"
> 0x000007000000-0x000007800000 : "errlog"
> mtdoops: Attached to MTD device 1
> mtdoops: ready 0, 1
> 0x000007800000-0x000008000000 : "nand-bbt"
>
> And from my attempt to mount:
>
> [root@linuxbox ~]# umount /flash && ubiattach -p /dev/mtd0 && mount -t
> ubifs ubi
> 0:user -o sync /flash
> ubi0: attaching mtd0
> ubi0: scanning is finished
> ubi0 error: ubi_read_volume_table: the layout volume was not found
> ubi0 error: ubi_attach_mtd_dev: failed to attach mtd0, error -22
> ubiattach: error!: cannot attach "/dev/mtd0"
> error 22 (Invalid argument)
> [root@linuxbox ~]#
>
>
> > ---
> > drivers/mtd/nand/raw/nand_micron.c | 25 ++++++++++++++++---------
> > 1 file changed, 16 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/mtd/nand/raw/nand_micron.c b/drivers/mtd/nand/raw/nand_micron.c
> > index 63ac98a36ed7..b9cbaf125a98 100644
> > --- a/drivers/mtd/nand/raw/nand_micron.c
> > +++ b/drivers/mtd/nand/raw/nand_micron.c
> > @@ -197,30 +197,37 @@ micron_nand_read_page_on_die_ecc(struct mtd_info *mtd, struct nand_chip *chip,
> >
> > ret = nand_read_page_op(chip, page, 0, NULL, 0);
> > if (ret)
> > - goto out;
> > + goto err_disable_ecc;
> >
> > ret = nand_status_op(chip, &status);
> > if (ret)
> > - goto out;
> > + goto err_disable_ecc;
> >
> > ret = nand_exit_status_op(chip);
> > if (ret)
> > - goto out;
> > + goto err_disable_ecc;
> >
> > - if (chip->ecc.strength == 4)
> > - max_bitflips = micron_nand_on_die_ecc_status_4(chip, status);
> > - else
> > - max_bitflips = micron_nand_on_die_ecc_status_8(chip, status);
> > + micron_nand_on_die_ecc_setup(chip, false);
Hm, can you try to move the micron_nand_on_die_ecc_setup(chip, false)
call just before nand_exit_status_op()?
> >
> > ret = nand_read_data_op(chip, buf, mtd->writesize, false);
> > if (!ret && oob_required)
> > ret = nand_read_data_op(chip, chip->oob_poi, mtd->oobsize,
> > false);
> >
> > -out:
> > + if (ret)
> > + return ret;
> > +
> > + if (chip->ecc.strength == 4)
> > + max_bitflips = micron_nand_on_die_ecc_status_4(chip, status);
> > + else
> > + max_bitflips = micron_nand_on_die_ecc_status_8(chip, status);
> > +
> > + return max_bitflips;
> > +
> > +err_disable_ecc:
> > micron_nand_on_die_ecc_setup(chip, false);
> >
> > - return ret ? ret : max_bitflips;
> > + return ret;
> > }
> >
> > static int
> >
>
next prev parent reply other threads:[~2018-07-16 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 12:20 [PATCH 0/3] mtd: rawnand: micron: Get the actual number of bitflips Boris Brezillon
2018-07-03 12:20 ` [PATCH 1/3] mtd: rawnand: micron: Stop passing mtd to ecc_status() funcs Boris Brezillon
2018-07-03 12:20 ` [PATCH 2/3] mtd: rawnand: micron: Disable ECC earlier in the read path Boris Brezillon
2018-07-16 9:00 ` [2/3] " Chris Packham
2018-07-16 16:10 ` Boris Brezillon [this message]
2018-07-16 20:55 ` Boris Brezillon
2018-07-16 22:42 ` Chris Packham
2018-07-17 11:41 ` Boris Brezillon
2018-07-17 21:27 ` Chris Packham
2018-07-17 21:31 ` Boris Brezillon
2018-07-18 7:25 ` Miquel Raynal
2018-07-03 12:20 ` [PATCH 3/3] mtd: rawnand: micron: Get the actual number of bitflips Boris Brezillon
2018-07-08 21:48 ` [PATCH 0/3] " Miquel Raynal
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=20180716181057.65d78303@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=beanhuo@micron.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
/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).