Hi Ezequiel, >From: Ezequiel Garcia [mailto:ezequiel.garcia@xxxxxxxxxxxxxxxxxx] >> diff --git a/Documentation/devicetree/bindings/mtd/nand.txt b/Documentation/devicetree/bindings/mtd/nand.txt >> index 03855c8..683a310 100644 >> --- a/Documentation/devicetree/bindings/mtd/nand.txt >> +++ b/Documentation/devicetree/bindings/mtd/nand.txt >> @@ -3,5 +3,9 @@ >> - nand-ecc-mode : String, operation mode of the NAND ecc mode. >> Supported values are: "none", "soft", "hw", "hw_syndrome", "hw_oob_first", >> "soft_bch". >> Should nand-ecc-mode also be marked as <deprecated>, and but we continue supporting it in kernel code ? If yes, then what is the life-time of these <deprecated> bindings. I mean exactly how many kernel versions should continue support deprecated bindings ? >> +- nand-ecc-strength : integer ECC required strength. With recent patches from 'Boris BREZILLON <b.brezillon.dev@xxxxxxxxx>' "[RFC PATCH] mtd: add per NAND partition ECC config" Would you like 'nand-ecc-strength' to be per partition based ? with regards, pekon ��.n��������+%������w��{.n����z�{��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
