On Thu, 21 Feb 2019 13:57:56 +0100 Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote: > There is no reason to always embed the software Hamming ECC engine > implementation. By default it is, but we can let the user decide. > > Signed-off-by: Miquel Raynal <miquel.raynal@xxxxxxxxxxx> > --- > drivers/mtd/nand/ecc/Kconfig | 10 +++++- > drivers/mtd/nand/raw/Kconfig | 2 +- > include/linux/mtd/nand-sw-hamming-engine.h | 38 ++++++++++++++++++++++ > 3 files changed, 48 insertions(+), 2 deletions(-) > > diff --git a/drivers/mtd/nand/ecc/Kconfig b/drivers/mtd/nand/ecc/Kconfig > index e0106b3a7ec1..ff20e621ffef 100644 > --- a/drivers/mtd/nand/ecc/Kconfig > +++ b/drivers/mtd/nand/ecc/Kconfig > @@ -1,7 +1,15 @@ > menu "ECC engine support" > > config MTD_NAND_ECC_SW_HAMMING > - tristate > + tristate "Software Hamming ECC engine" > + default y Same as for the NAND_CORE stuff, let users this option when they need it instead of having a "default y". Haven't made my mind yet on whether this option should be visible to users or not. I guess it could be with the new infrastructure, but it's probably too early in the patch series to change that. > + help > + This enables support for software Hamming error > + correction. This correction can correct up to 1 bit error > + per chunk and detect up to 2 bit errors. While it used to be > + widely used with old parts, newer NAND chips usually require > + more strength correction and in this case BCH or RS will be > + preferred. > ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/