Skip to content
Snippets Groups Projects
Commit 7d9ef7f3 authored by Rob Herring's avatar Rob Herring
Browse files

dt-bindings: riscv: Limit cpus schema to only check RiscV 'cpu' nodes


Matching on the 'cpus' node was a bad choice because the schema is
incorrectly applied to non-RiscV cpus nodes. As we now have a common cpus
schema which checks the general structure, it is also redundant to do so
in the Risc-V CPU schema.

The downside is one could conceivably mix different architecture's cpu
nodes or have typos in the compatible string. The latter problem pretty
much exists for every schema.

Acked-by: default avatarPaul Walmsley <paul.walmsley@sifive.com>
Signed-off-by: default avatarRob Herring <robh@kernel.org>
parent 15ffef1a
No related branches found
No related tags found
No related merge requests found
...@@ -10,29 +10,8 @@ maintainers: ...@@ -10,29 +10,8 @@ maintainers:
- Paul Walmsley <paul.walmsley@sifive.com> - Paul Walmsley <paul.walmsley@sifive.com>
- Palmer Dabbelt <palmer@sifive.com> - Palmer Dabbelt <palmer@sifive.com>
allOf:
- $ref: /schemas/cpus.yaml#
properties:
$nodename:
const: cpus
description: Container of cpu nodes
'#address-cells':
const: 1
description: |
A single unsigned 32-bit integer uniquely identifies each RISC-V
hart in a system. (See the "reg" node under the "cpu" node,
below).
'#size-cells':
const: 0
patternProperties:
'^cpu@[0-9a-f]+$':
properties: properties:
compatible: compatible:
type: array
items: items:
- enum: - enum:
- sifive,rocket0 - sifive,rocket0
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment