[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CABMhjYpUn4VGku+WQ1cVdbQJWp6sVfkoQg5C2PVZYyaDybA_Aw@mail.gmail.com>
Date: Wed, 20 Apr 2022 22:07:44 -0700
From: Atul Khare <atulkhare@...osinc.com>
To: linux-kernel@...r.kernel.org
Cc: stable@...r.kernel.org
Subject: [PATCH 2/4] dt-bindings: sifive: add cache-set value of 2048
Fixes Running device tree schema validation error messages like
'... cache-sets:0:0: 1024 was expected'.
The existing bindings had a single enumerated value of 1024, which
trips up the dt-schema checks. The ISA permits any arbitrary power
of two for the cache-sets value, but we decided to add the single
additional value of 2048 because we couldn't spot an obvious way
to express the constraint in the schema.
Fixes: a2770b57d083 ("dt-bindings: timer: Add CLINT bindings")
Cc: stable@...r.kernel.org
Signed-off-by: Atul Khare <atulkhare@...osinc.com>
---
Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml
b/Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml
index e2d330bd4608..309517b78e84 100644
--- a/Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml
+++ b/Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml
@@ -46,7 +46,9 @@ properties:
const: 2
cache-sets:
- const: 1024
+ # Note: Technically this can be any power of 2, but we didn't see
an obvious way
+ # to express the constraint in Yaml
+ enum: [1024, 2048]
cache-size:
const: 2097152
--
2.35.1
Powered by blists - more mailing lists