[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <166863220434.867607.9322853555110461989.robh@kernel.org>
Date: Wed, 16 Nov 2022 14:56:44 -0600
From: Rob Herring <robh@...nel.org>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Richard Weinberger <richard@....at>,
linux-kernel@...r.kernel.org,
Vignesh Raghavendra <vigneshr@...com>,
devicetree@...r.kernel.org,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Pratyush Yadav <pratyush@...nel.org>,
Tudor Ambarus <Tudor.Ambarus@...rochip.com>,
linux-mtd@...ts.infradead.org, Michael Walle <michael@...le.cc>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH v3 13/17] dt-bindings: mtd: nvmem-cells: Drop range
property from example
On Mon, 14 Nov 2022 10:03:11 +0100, Miquel Raynal wrote:
> Memory mapped devices such as parallel NOR flash could make use of the
> 'ranges' property to translate a nvmem 'reg' cell address to a CPU
> address but in practice there is no upstream user nor any declaration of
> this property being valid in this case yet, leading to a warning when
> constraining a bit more the schema:
>
> .../mtd/partitions/nvmem-cells.example.dtb: calibration@...000:
> Unevaluated properties are not allowed ('ranges' was unexpected)
>
> So let's drop the property from the example, knowing that someone might
> actually properly define it some day.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@...tlin.com>
> ---
> .../devicetree/bindings/mtd/partitions/nvmem-cells.yaml | 1 -
> 1 file changed, 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists