From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Peter Pan <peterpandong@micron.com>
Cc: <richard@nod.at>, <computersforpeace@gmail.com>,
<arnaud.mouiche@gmail.com>, <thomas.petazzoni@free-electrons.com>,
<marex@denx.de>, <cyrille.pitchen@atmel.com>,
<linux-mtd@lists.infradead.org>, <peterpansjtu@gmail.com>,
<linshunquan1@hisilicon.com>
Subject: Re: [PATCH v5 3/6] nand: spi: Add bad block support
Date: Mon, 17 Apr 2017 23:23:14 +0200 [thread overview]
Message-ID: <20170417232314.3e9b481d@bbrezillon> (raw)
In-Reply-To: <1491810713-27795-4-git-send-email-peterpandong@micron.com>
On Mon, 10 Apr 2017 15:51:50 +0800
Peter Pan <peterpandong@micron.com> wrote:
> +
> +/*
> + * spinand_scan_bbt - scan BBT in SPI NAND device
> + * @chip: SPI NAND device structure
> + */
> +static int spinand_scan_bbt(struct spinand_device *chip)
> +{
> + struct nand_device *nand = &chip->base;
> + int ret;
> +
> + /*
> + * It's better to put BBT marker in-band, since some oob area
> + * is not ecc protected by internal(on-die) ECC
> + */
> + if (nand->bbt.options & NAND_BBT_USE_FLASH)
> + nand->bbt.options |= NAND_BBT_NO_OOB;
Hm, really? Do we want to force NAND_BBT_NO_OOB for everyone?
> + nand->bbt.td = NULL;
> + nand->bbt.md = NULL;
> +
> + ret = spinand_create_badblock_pattern(chip);
> + if (ret)
> + return ret;
> +
> + return nand_scan_bbt(nand);
> +}
> +
[...]
> /*
> @@ -1085,13 +1383,14 @@ static int spinand_init(struct spinand_device *chip)
> GFP_KERNEL);
> if (!chip->buf) {
> ret = -ENOMEM;
> - goto err;
> + goto err1;
> }
>
> chip->oobbuf = chip->buf + nand_page_size(nand);
>
> spinand_manufacturer_init(chip);
>
> + nand->ops = &spinand_ops;
> mtd->name = chip->name;
> mtd->size = nand_size(nand);
> mtd->erasesize = nand_eraseblock_size(nand);
> @@ -1109,11 +1408,14 @@ static int spinand_init(struct spinand_device *chip)
> if (ret < 0)
> ret = 0;
> mtd->oobavail = ret;
> - mtd->_erase = spinand_erase;
> + mtd->_erase = spinand_erase_skip_bbt;
> mtd->_read = spinand_read;
> mtd->_write = spinand_write;
> mtd->_read_oob = spinand_read_oob;
> mtd->_write_oob = spinand_write_oob;
> + mtd->_block_isbad = spinand_block_isbad;
> + mtd->_block_markbad = spinand_block_markbad;
> + mtd->_block_isreserved = spinand_block_isreserved;
>
> if (!mtd->bitflip_threshold)
> mtd->bitflip_threshold = DIV_ROUND_UP(mtd->ecc_strength * 3,
> @@ -1121,9 +1423,18 @@ static int spinand_init(struct spinand_device *chip)
> /* After power up, all blocks are locked, so unlock it here. */
> spinand_lock_block(chip, BL_ALL_UNLOCKED);
>
> + /* Build bad block table */
> + ret = spinand_scan_bbt(chip);
> + if (ret) {
> + dev_err(chip->dev, "Scan Bad Block Table failed.\n");
> + goto err2;
> + }
> +
> return nand_register(nand);
>
> -err:
> +err2:
General note: please use better descriptions for your labels, like
err_free_buf
> + devm_kfree(chip->dev, chip->buf);
This is not needed (automatically released).
> +err1:
> return ret;
> }
>
> @@ -1191,10 +1502,14 @@ int spinand_register(struct spinand_device *chip)
> int spinand_unregister(struct spinand_device *chip)
> {
> struct nand_device *nand = &chip->base;
> + struct nand_bbt_descr *bd = nand->bbt.bbp;
>
> nand_unregister(nand);
> spinand_manufacturer_cleanup(chip);
> devm_kfree(chip->dev, chip->buf);
> + kfree(nand->bbt.bbt);
> + if (bd->options & NAND_BBT_DYNAMICSTRUCT)
> + devm_kfree(chip->dev, bd);
Ditto.
>
> return 0;
> }
next prev parent reply other threads:[~2017-04-17 21:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 7:51 [PATCH v5 0/6] Introduction to SPI NAND framework Peter Pan
2017-04-10 7:51 ` [PATCH v5 1/6] nand: spi: add basic blocks for infrastructure Peter Pan
2017-04-10 8:28 ` Boris Brezillon
2017-04-14 13:18 ` Marek Vasut
2017-04-17 20:34 ` Boris Brezillon
2017-04-17 20:53 ` Boris Brezillon
2017-04-18 7:29 ` Boris Brezillon
2017-04-10 7:51 ` [PATCH v5 2/6] nand: spi: add basic operations support Peter Pan
2017-04-17 21:05 ` Boris Brezillon
2017-04-10 7:51 ` [PATCH v5 3/6] nand: spi: Add bad block support Peter Pan
2017-04-17 21:23 ` Boris Brezillon [this message]
2017-04-10 7:51 ` [PATCH v5 4/6] nand: spi: add Micron spi nand support Peter Pan
2017-04-14 13:23 ` Marek Vasut
2017-04-18 7:20 ` Boris Brezillon
2017-04-10 7:51 ` [PATCH v5 5/6] nand: spi: Add generic SPI controller support Peter Pan
2017-04-14 13:26 ` Marek Vasut
2017-04-18 7:41 ` Boris Brezillon
2017-04-18 7:26 ` Boris Brezillon
2017-04-10 7:51 ` [PATCH v5 6/6] MAINTAINERS: Add SPI NAND entry Peter Pan
2017-04-18 7:42 ` [PATCH v5 0/6] Introduction to SPI NAND framework Boris Brezillon
2017-04-19 6:01 ` Peter Pan
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=20170417232314.3e9b481d@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=arnaud.mouiche@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=linshunquan1@hisilicon.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=peterpandong@micron.com \
--cc=peterpansjtu@gmail.com \
--cc=richard@nod.at \
--cc=thomas.petazzoni@free-electrons.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