On Tue, 26 May 2020 21:56:27 +0200 Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote: > This mode should not be used anymore, it is actually a mix between a > mode and a placement. > > Signed-off-by: Miquel Raynal <miquel.raynal@xxxxxxxxxxx> > --- > Documentation/devicetree/bindings/mtd/nand-controller.yaml | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/mtd/nand-controller.yaml b/Documentation/devicetree/bindings/mtd/nand-controller.yaml > index 35512f2c66fa..a35ff8227427 100644 > --- a/Documentation/devicetree/bindings/mtd/nand-controller.yaml > +++ b/Documentation/devicetree/bindings/mtd/nand-controller.yaml > @@ -49,12 +49,14 @@ patternProperties: > nand-ecc-mode: > allOf: > - $ref: /schemas/types.yaml#/definitions/string > - - enum: [ none, soft, hw, hw_syndrome, on-die ] > + - enum: [ none, soft, hw, on-die ] > description: > Desired ECC engine, either hardware (most of the time > embedded in the NAND controller) or software correction > (Linux will handle the calculations). soft_bch is deprecated > and should be replaced by soft and nand-ecc-algo. > + hw_syndrome is deprecated and should be > + replaced by hw and nand-ecc-placement. Well, I'd expect the whole property to be deprecated in favor of nand-ecc-engine-type. > > nand-ecc-placement: > allOf:
