summaryrefslogtreecommitdiffstats
path: root/drivers/mtd/nand/Makefile
diff options
context:
space:
mode:
authorMiquel Raynal <miquel.raynal@bootlin.com>2020-08-27 10:51:56 +0200
committerMiquel Raynal <miquel.raynal@bootlin.com>2020-09-02 09:28:15 +0200
commita8c7ffdb5fdde3a57c0b654f66f4d81325abe69f (patch)
tree8efed3aacb084db560bfb9e5f04f074fb7073391 /drivers/mtd/nand/Makefile
parentdt-bindings: mtd: Document boolean NAND ECC properties (diff)
downloadlinux-a8c7ffdb5fdde3a57c0b654f66f4d81325abe69f.tar.xz
linux-a8c7ffdb5fdde3a57c0b654f66f4d81325abe69f.zip
mtd: nand: Introduce the ECC engine framework
Create a generic ECC engine framework. This is a base to instantiate ECC engine objects. If we really want to be generic, bindings must evolve, so here is the new logic. The following three properties are mutually exclusive: - The nand-no-ecc-engine boolean property is set and there is no ECC engine to retrieve. - The nand-use-soft-ecc-engine boolean property is set and the core will force using the use of software correction. - There is a nand-ecc-engine property pointing at a node which will act as ECC engine. It the later case, the property may reference: - The NAND chip node itself (for the on-die ECC case). - The parent node if the NAND controller embeds an ECC engine. - Any other node being an external ECC controller as well. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Link: https://lore.kernel.org/linux-mtd/20200827085208.16276-9-miquel.raynal@bootlin.com
Diffstat (limited to 'drivers/mtd/nand/Makefile')
-rw-r--r--drivers/mtd/nand/Makefile2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/mtd/nand/Makefile b/drivers/mtd/nand/Makefile
index 7ecd80c0a66e..981372953b56 100644
--- a/drivers/mtd/nand/Makefile
+++ b/drivers/mtd/nand/Makefile
@@ -6,3 +6,5 @@ obj-$(CONFIG_MTD_NAND_CORE) += nandcore.o
obj-y += onenand/
obj-y += raw/
obj-y += spi/
+
+nandcore-$(CONFIG_MTD_NAND_ECC) += ecc.o