diff options
| author | Miquel Raynal <[email protected]> | 2023-06-19 11:29:00 +0200 |
|---|---|---|
| committer | Miquel Raynal <[email protected]> | 2023-06-22 23:03:21 +0200 |
| commit | da787688a5a08ece05a2f752d38b281fab8df846 (patch) | |
| tree | 6f1971bb18545ab966276cabf5adc50be57f3595 | |
| parent | e87161321a4081d36c4af95af7f0950137569dfe (diff) | |
dt-bindings: mtd: Accept nand related node names
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 <[email protected]>
Reviewed-by: Rob Herring <[email protected]>
Reviewed-by: Krzysztof Kozlowski <[email protected]>
Link: https://lore.kernel.org/linux-mtd/[email protected]
| -rw-r--r-- | Documentation/devicetree/bindings/mtd/mtd.yaml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/mtd/mtd.yaml b/Documentation/devicetree/bindings/mtd/mtd.yaml index da3d488c335f..b82ca03e969c 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: |