| Message ID | 20230606175246.190465-2-miquel.raynal@bootlin.com |
|---|---|
| State | Accepted |
| Commit | da787688a5a08ece05a2f752d38b281fab8df846 |
| Headers | show |
| Series | [v2,01/17] dt-bindings: mtd: Accept nand related node names | expand |
On 06/06/2023 19:52, Miquel Raynal wrote: > There is no addition there, but the mtd.yaml file is so generic, it can > be referenced by a wide variety of devices, including nand ones which > already define the node name to "nand@<cs>". Right now it does not lead > to any failure but when we will constrain more the schema, this will > become a problem because we want the mtd-wide properties like label or > partitions to be available for the callers. > > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> > --- Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
diff --git a/Documentation/devicetree/bindings/mtd/mtd.yaml b/Documentation/devicetree/bindings/mtd/mtd.yaml index 78da129e9985..589481b0b93d 100644 --- a/Documentation/devicetree/bindings/mtd/mtd.yaml +++ b/Documentation/devicetree/bindings/mtd/mtd.yaml @@ -12,7 +12,7 @@ maintainers: properties: $nodename: - pattern: "^(flash|.*sram)(@.*)?$" + pattern: "^(flash|.*sram|nand)(@.*)?$" label: description:
There is no addition there, but the mtd.yaml file is so generic, it can be referenced by a wide variety of devices, including nand ones which already define the node name to "nand@<cs>". Right now it does not lead to any failure but when we will constrain more the schema, this will become a problem because we want the mtd-wide properties like label or partitions to be available for the callers. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> --- Documentation/devicetree/bindings/mtd/mtd.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)