From: Boris Brezillon <boris.brezillon@collabora.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <Tudor.Ambarus@microchip.com>,
Julien Su <juliensu@mxic.com.tw>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Mason Yang <masonccyang@mxic.com.tw>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v9 0/9] Preparation to the generic ECC engine abstraction
Date: Tue, 2 Jun 2020 18:33:36 +0200 [thread overview]
Message-ID: <20200602183336.5447d34a@collabora.com> (raw)
In-Reply-To: <20200602143124.29553-1-miquel.raynal@bootlin.com>
On Tue, 2 Jun 2020 16:31:15 +0200
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> This is a respin of the end of my previous series, just the patches which needed to be fixed.
>
> Changes in v9:
> * This time sending the additional patchs, not just the old ones with
> corrections. v8 should be ignored, sorry for the noise.
>
> Changes in v8:
> * Split "Convert generic NAND bits to ECC framework" into several peaces:
> > added two helpers
> > converted SPI-NAND then raw-NAND.
> * Fixed a comment.
> * Used the _ooblayout suffix instead of _layout.
>
>
> Miquel Raynal (9):
> mtd: nand: Create a helper to extract the ECC configuration
> mtd: spinand: Use nanddev_get_ecc_conf() when relevant
> mtd: nand: Create a helper to extract the ECC requirements
> mtd: rawnand: Use nanddev_get_ecc_requirements() when relevant
> mtd: nand: Convert generic NAND bits to use the ECC framework
> mtd: rawnand: Hide the generic OOB layout objects behind helpers
> mtd: rawnand: Write a compatibility layer
> mtd: rawnand: Move generic OOB layouts to the ECC framework
> mtd: rawnand: Move the user input parsing bits to the ECC framework
Sorry, but I keep thinking you should re-order things so we don't have
code blocks introduced and then moved around in the same patchset.
What's the point of introducing new props/helpers in rawnand if the
ultimate goal is to move them to nand.h, especially since none of the
existing rawnand drivers (or the rawnand core) need those new DT props
right now. You should really consider doing that in 3 distinct steps:
1/ Introduce ECC related fields/defs/... at the generic NAND level
2/ Patch rawnand to use those fields/new defs and deprecate the old ones
3/ Move rawnand defs/code that can be made generic and be useful to
!rawnand users
>
> drivers/mtd/nand/ecc.c | 314 ++++++++++++++
> drivers/mtd/nand/raw/Kconfig | 1 +
> drivers/mtd/nand/raw/arasan-nand-controller.c | 2 +-
> drivers/mtd/nand/raw/atmel/nand-controller.c | 15 +-
> drivers/mtd/nand/raw/brcmnand/brcmnand.c | 8 +-
> drivers/mtd/nand/raw/davinci_nand.c | 3 +-
> drivers/mtd/nand/raw/denali.c | 3 +
> drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c | 13 +-
> .../mtd/nand/raw/ingenic/ingenic_nand_drv.c | 6 +-
> drivers/mtd/nand/raw/marvell_nand.c | 8 +-
> drivers/mtd/nand/raw/mtk_nand.c | 6 +-
> drivers/mtd/nand/raw/nand_base.c | 395 ++++--------------
> drivers/mtd/nand/raw/nand_esmt.c | 14 +-
> drivers/mtd/nand/raw/nand_hynix.c | 43 +-
> drivers/mtd/nand/raw/nand_jedec.c | 7 +-
> drivers/mtd/nand/raw/nand_micron.c | 17 +-
> drivers/mtd/nand/raw/nand_onfi.c | 14 +-
> drivers/mtd/nand/raw/nand_samsung.c | 21 +-
> drivers/mtd/nand/raw/nand_toshiba.c | 15 +-
> drivers/mtd/nand/raw/sunxi_nand.c | 9 +-
> drivers/mtd/nand/raw/tegra_nand.c | 15 +-
> drivers/mtd/nand/raw/vf610_nfc.c | 2 +-
> drivers/mtd/nand/spi/core.c | 10 +-
> drivers/mtd/nand/spi/macronix.c | 7 +-
> drivers/mtd/nand/spi/toshiba.c | 6 +-
> include/linux/mtd/nand.h | 40 +-
> include/linux/mtd/rawnand.h | 17 +-
> 27 files changed, 587 insertions(+), 424 deletions(-)
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-06-02 16:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 14:31 [PATCH v9 0/9] Preparation to the generic ECC engine abstraction Miquel Raynal
2020-06-02 14:31 ` [PATCH v9 1/9] mtd: nand: Create a helper to extract the ECC configuration Miquel Raynal
2020-06-02 15:51 ` Boris Brezillon
2020-06-02 14:31 ` [PATCH v9 2/9] mtd: spinand: Use nanddev_get_ecc_conf() when relevant Miquel Raynal
2020-06-02 14:31 ` [PATCH v9 3/9] mtd: nand: Create a helper to extract the ECC requirements Miquel Raynal
2020-06-02 14:31 ` [PATCH v9 4/9] mtd: rawnand: Use nanddev_get_ecc_requirements() when relevant Miquel Raynal
2020-06-02 16:00 ` Boris Brezillon
2020-06-03 10:30 ` Miquel Raynal
2020-06-02 14:31 ` [PATCH v9 5/9] mtd: nand: Convert generic NAND bits to use the ECC framework Miquel Raynal
2020-06-02 16:03 ` Boris Brezillon
2020-06-03 10:29 ` Miquel Raynal
2020-06-02 14:31 ` [PATCH v9 6/9] mtd: rawnand: Hide the generic OOB layout objects behind helpers Miquel Raynal
2020-06-02 16:05 ` Boris Brezillon
2020-06-02 14:31 ` [PATCH v9 7/9] mtd: rawnand: Write a compatibility layer Miquel Raynal
2020-06-02 14:31 ` [PATCH v9 8/9] mtd: rawnand: Move generic OOB layouts to the ECC framework Miquel Raynal
2020-06-02 14:31 ` [PATCH v9 9/9] mtd: rawnand: Move the user input parsing bits " Miquel Raynal
2020-06-02 16:18 ` Boris Brezillon
2020-06-02 16:21 ` Boris Brezillon
2020-06-03 12:58 ` Miquel Raynal
2020-06-03 13:05 ` Boris Brezillon
2020-06-02 16:23 ` Boris Brezillon
2020-06-02 16:33 ` Boris Brezillon [this message]
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=20200602183336.5447d34a@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=juliensu@mxic.com.tw \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=masonccyang@mxic.com.tw \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=thomas.petazzoni@bootlin.com \
--cc=vigneshr@ti.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).