[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220518181100.GG3302100-robh@kernel.org>
Date: Wed, 18 May 2022 13:11:00 -0500
From: Rob Herring <robh@...nel.org>
To: Ansuel Smith <ansuelsmth@...il.com>
Cc: Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Manivannan Sadhasivam <mani@...nel.org>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-mtd@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: mtd: qcom_nandc: document
qcom,boot-pages binding
On Tue, May 17, 2022 at 10:56:09PM +0200, Ansuel Smith wrote:
> On Mon, May 16, 2022 at 01:49:12PM -0500, Rob Herring wrote:
> > On Tue, May 03, 2022 at 05:43:53PM +0200, Ansuel Smith wrote:
> > > Document new qcom,boot_pages binding used to apply special
> >
> > s/boot_pages/boot-pages/
> >
> > > read/write configuration to boot pages.
> > >
> > > QCOM apply a special configuration where spare data is not protected
> > > by ECC for some special pages (used for boot partition). Add
> > > Documentation on how to declare these special pages.
> > >
> > > Signed-off-by: Ansuel Smith <ansuelsmth@...il.com>
> > > ---
> > > .../devicetree/bindings/mtd/qcom,nandc.yaml | 22 +++++++++++++++++++
> > > 1 file changed, 22 insertions(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/mtd/qcom,nandc.yaml b/Documentation/devicetree/bindings/mtd/qcom,nandc.yaml
> > > index 84ad7ff30121..fafeca0cafff 100644
> > > --- a/Documentation/devicetree/bindings/mtd/qcom,nandc.yaml
> > > +++ b/Documentation/devicetree/bindings/mtd/qcom,nandc.yaml
> > > @@ -102,6 +102,26 @@ allOf:
> > > - const: rx
> > > - const: cmd
> > >
> > > + - if:
> > > + properties:
> > > + compatible:
> > > + contains:
> > > + enum:
> > > + - qcom,ipq8074-nand
> > > +
> > > + then:
> > > + properties:
> > > + qcom,boot-pages:
> > > + $ref: /schemas/types.yaml#/definitions/uint32-matrix
> >
> > You need to define the dimensions. Something like this:
> >
> > items:
> > items:
> > - description: offset
> > - description: size
> >
>
> Considering this is not limited to one item how should I declare that an
> user can declare multiple items? (the user can declare multiple zones)
> Declaring minItems without a maxItems?
>
> I assume in the suggested form it's assumed
> minItems: 1
> maxItems: 1
> so this would be problematic.
No, the outer 'items' being a schema rather than a list means it applies
to all items and does not set a size of (offset, size) pairs.
If you do have a maximum number, you could set the range.
Rob
Powered by blists - more mailing lists