Add device nodes for the L2 caches, and link the CPU node to its L2
cache node.

The L2 cache for the Cortex-A15 CPU cores is 1 MiB large (organized as
64 KiB x 16 ways), and located in PM domain A3SM. It requires the
following settings:
  - Tag RAM latency: 3 cycles,
  - Data RAM latency: 4 cycles.

The L2 cache for the Cortex-A7 CPU cores is 512 KiB large (organized as
64 KiB x 8 ways), and located in PM domain A3KM.

Signed-off-by: Geert Uytterhoeven <[email protected]>
---
What are the DT bindings for Cortex-A15/A7 L2 cache controllers?

v2:
  - New.
---
 arch/arm/boot/dts/r8a73a4.dtsi | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/arch/arm/boot/dts/r8a73a4.dtsi b/arch/arm/boot/dts/r8a73a4.dtsi
index 86fab56cd6314df7..73f7ea3cb2209a00 100644
--- a/arch/arm/boot/dts/r8a73a4.dtsi
+++ b/arch/arm/boot/dts/r8a73a4.dtsi
@@ -29,6 +29,7 @@
                        reg = <0>;
                        clock-frequency = <1500000000>;
                        power-domains = <&pd_a2sl>;
+                       next-level-cache = <&L2_CA15>;
                };
        };
 
@@ -45,6 +46,24 @@
                             <1 10 (GIC_CPU_MASK_SIMPLE(4) | 
IRQ_TYPE_LEVEL_LOW)>;
        };
 
+       L2_CA15: cache-controller@0 {
+               compatible = "cache";
+               clocks = <&cpg_clocks R8A73A4_CLK_Z>;
+               power-domains = <&pd_a3sm>;
+               arm,data-latency = <4 4 0>;
+               arm,tag-latency = <3 3 3>;
+               cache-unified;
+               cache-level = <2>;
+       };
+
+       L2_CA7: cache-controller@1 {
+               compatible = "cache";
+               clocks = <&cpg_clocks R8A73A4_CLK_Z2>;
+               power-domains = <&pd_a3km>;
+               cache-unified;
+               cache-level = <2>;
+       };
+
        dbsc1: memory-controller@e6790000 {
                compatible = "renesas,dbsc-r8a73a4";
                reg = <0 0xe6790000 0 0x10000>;
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to