| Message ID | 20221114090315.848208-14-miquel.raynal@bootlin.com |
|---|---|
| State | Accepted |
| Headers | show |
| Series | Improve MTD bindings | expand |
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@f00000: > 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@bootlin.com> > --- > .../devicetree/bindings/mtd/partitions/nvmem-cells.yaml | 1 - > 1 file changed, 1 deletion(-) > Reviewed-by: Rob Herring <robh@kernel.org>
On Mon, 2022-11-14 at 09:03:11 UTC, 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@f00000: > 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@bootlin.com> > Reviewed-by: Rob Herring <robh@kernel.org> Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next. Miquel
diff --git a/Documentation/devicetree/bindings/mtd/partitions/nvmem-cells.yaml b/Documentation/devicetree/bindings/mtd/partitions/nvmem-cells.yaml index 5cdd2efa9132..ca18892eacc7 100644 --- a/Documentation/devicetree/bindings/mtd/partitions/nvmem-cells.yaml +++ b/Documentation/devicetree/bindings/mtd/partitions/nvmem-cells.yaml @@ -84,7 +84,6 @@ examples: compatible = "nvmem-cells"; label = "calibration"; reg = <0xf00000 0x100000>; - ranges = <0 0xf00000 0x100000>; #address-cells = <1>; #size-cells = <1>;
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@f00000: 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@bootlin.com> --- .../devicetree/bindings/mtd/partitions/nvmem-cells.yaml | 1 - 1 file changed, 1 deletion(-)