The CM3.5 used on EyeQ6 reports that Hardware Cache Initialization is
complete, but in reality it's not the case. It also incorrectly
indicates that Hardware Cache Initialization is supported. This new
compatible string allows warning about this broken feature that cannot
be detected at runtime.
Signed-off-by: Gregory CLEMENT <gregory.clement@xxxxxxxxxxx>
---
.../devicetree/bindings/mips/mti,mips-cm.yaml | 24 ++++++++++++++++++++--
1 file changed, 22 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml b/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
index 9f500804737d23e19f50a9326168686c05d3a54e..4713673f0cfc7785bb183917ee382a815ebfe9e1 100644
--- a/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
+++ b/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
@@ -14,7 +14,12 @@ maintainers:
properties:
compatible:
- const: mti,mips-cm
+ oneOf:
+ - const: mti,mips-cm
+ - const: mti,eyeq6-cm
+ description:
+ On EyeQ6 the HCI (Hardware Cache Initialization) information for
+ the L2 cache in multi-cluster configuration is broken.
reg:
description:
@@ -25,14 +30,29 @@ properties:
required:
- compatible
- - reg
additionalProperties: false
+if:
+ properties:
+ compatible:
+ contains:
+ const: mti,eyeq6-cm
+then:
+ properties:
+ reg: false
+else:
+ required:
+ - reg
+
examples:
- |
coherency-manager@1fbf8000 {
compatible = "mti,mips-cm";
reg = <0x1bde8000 0x8000>;
};
+
+ coherency-manager {
+ compatible = "mti,eyeq6-cm";
+ };
...
--
2.45.2
