Despite its current name "eccreq", this object first stores data that is meant to be the requirements, and then this data gets eventually updated and becomes the actual configuration. Abstracting this indirection will help us clarify the structures in a future change. Signed-off-by: Miquel Raynal <miquel.raynal@xxxxxxxxxxx> --- include/linux/mtd/nand.h | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h index 2f838394b5f7..7fd0d492073b 100644 --- a/include/linux/mtd/nand.h +++ b/include/linux/mtd/nand.h @@ -512,6 +512,16 @@ nanddev_get_memorg(struct nand_device *nand) return &nand->memorg; } +/** + * nanddev_get_ecc_conf() - Extract the ECC configuration from a NAND device + * @nand: NAND device + */ +static inline const struct nand_ecc_props * +nanddev_get_ecc_conf(struct nand_device *nand) +{ + return &nand->eccreq; +} + int nanddev_init(struct nand_device *nand, const struct nand_ops *ops, struct module *owner); void nanddev_cleanup(struct nand_device *nand); -- 2.20.1 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/