1 =======================================================
2 ARM CCI cache coherent interconnect binding description
3 =======================================================
5 ARM multi-cluster systems maintain intra-cluster coherency through a
6 cache coherent interconnect (CCI) that is capable of monitoring bus
7 transactions and manage coherency, TLB invalidations and memory barriers.
9 It allows snooping and distributed virtual memory message broadcast across
10 clusters, through memory mapped interface, with a global control register
11 space and multiple sets of interface control registers, one per slave
14 Bindings for the CCI node follow the ePAPR standard, available from:
16 www.power.org/documentation/epapr-version-1-1/
18 with the addition of the bindings described in this document which are
21 * CCI interconnect node
23 Description: Describes a CCI cache coherent Interconnect component
25 Node name must be "cci".
26 Node's parent must be the root node /, and the address space visible
27 through the CCI interconnect is the same as the one seen from the
28 root node (ie from CPUs perspective as per DT standard).
29 Every CCI node has to define the following properties:
34 Definition: must contain one of the following:
40 Value type: Integer cells. A register entry, expressed as a pair
41 of cells, containing base and size.
42 Definition: A standard property. Specifies base physical
43 address of CCI control registers common to all
48 Value type: Integer cells. An array of range entries, expressed
49 as a tuple of cells, containing child address,
50 parent address and the size of the region in the
52 Definition: A standard property. Follow rules in the ePAPR for
53 hierarchical bus addressing. CCI interfaces
54 addresses refer to the parent node addressing
55 scheme to declare their register bases.
57 CCI interconnect node can define the following child nodes:
59 - CCI control interface nodes
61 Node name must be "slave-if".
62 Parent node must be CCI interconnect node.
64 A CCI control interface node must contain the following
70 Definition: must be set to
76 Definition: must be set to one of {"ace", "ace-lite"}
77 depending on the interface type the node
82 Value type: Integer cells. A register entry, expressed
83 as a pair of cells, containing base and
85 Definition: the base address and size of the
86 corresponding interface programming
91 Parent node must be CCI interconnect node.
93 A CCI pmu node must contain the following properties:
98 Definition: Must contain one of:
101 "arm,cci-400-pmu" - DEPRECATED, permitted only where OS has
102 secure acces to CCI registers
106 Value type: Integer cells. A register entry, expressed
107 as a pair of cells, containing base and
109 Definition: the base address and size of the
110 corresponding interface programming
115 Value type: Integer cells. Array of interrupt specifier
116 entries, as defined in
117 ../interrupt-controller/interrupts.txt.
118 Definition: list of counter overflow interrupts, one per
119 counter. The interrupts must be specified
120 starting with the cycle counter overflow
121 interrupt, followed by counter0 overflow
122 interrupt, counter1 overflow interrupt,...
123 ,counterN overflow interrupt.
125 The CCI PMU has an interrupt signal for each
126 counter. The number of interrupts must be
127 equal to the number of counters.
129 * CCI interconnect bus masters
131 Description: masters in the device tree connected to a CCI port
132 (inclusive of CPUs and their cpu nodes).
134 A CCI interconnect bus master node must contain the following
139 Value type: <phandle>
140 Definition: a phandle containing the CCI control interface node
141 the master is connected to.
147 #address-cells = <1>;
151 compatible = "arm,cortex-a15";
152 cci-control-port = <&cci_control1>;
158 compatible = "arm,cortex-a15";
159 cci-control-port = <&cci_control1>;
165 compatible = "arm,cortex-a7";
166 cci-control-port = <&cci_control2>;
172 compatible = "arm,cortex-a7";
173 cci-control-port = <&cci_control2>;
180 compatible = "arm,pl330", "arm,primecell";
181 cci-control-port = <&cci_control0>;
182 reg = <0x0 0x3000000 0x0 0x1000>;
186 #dma-requests = <32>;
190 compatible = "arm,cci-400";
191 #address-cells = <1>;
193 reg = <0x0 0x2c090000 0 0x1000>;
194 ranges = <0x0 0x0 0x2c090000 0x10000>;
196 cci_control0: slave-if@1000 {
197 compatible = "arm,cci-400-ctrl-if";
198 interface-type = "ace-lite";
199 reg = <0x1000 0x1000>;
202 cci_control1: slave-if@4000 {
203 compatible = "arm,cci-400-ctrl-if";
204 interface-type = "ace";
205 reg = <0x4000 0x1000>;
208 cci_control2: slave-if@5000 {
209 compatible = "arm,cci-400-ctrl-if";
210 interface-type = "ace";
211 reg = <0x5000 0x1000>;
215 compatible = "arm,cci-400-pmu";
216 reg = <0x9000 0x5000>;
217 interrupts = <0 101 4>,
225 This CCI node corresponds to a CCI component whose control registers sits
226 at address 0x000000002c090000.
227 CCI slave interface @0x000000002c091000 is connected to dma controller dma0.
228 CCI slave interface @0x000000002c094000 is connected to CPUs {CPU0, CPU1};
229 CCI slave interface @0x000000002c095000 is connected to CPUs {CPU2, CPU3};