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 be set to
39 Value type: Integer cells. A register entry, expressed as a pair
40 of cells, containing base and size.
41 Definition: A standard property. Specifies base physical
42 address of CCI control registers common to all
47 Value type: Integer cells. An array of range entries, expressed
48 as a tuple of cells, containing child address,
49 parent address and the size of the region in the
51 Definition: A standard property. Follow rules in the ePAPR for
52 hierarchical bus addressing. CCI interfaces
53 addresses refer to the parent node addressing
54 scheme to declare their register bases.
56 CCI interconnect node can define the following child nodes:
58 - CCI control interface nodes
60 Node name must be "slave-if".
61 Parent node must be CCI interconnect node.
63 A CCI control interface node must contain the following
69 Definition: must be set to
75 Definition: must be set to one of {"ace", "ace-lite"}
76 depending on the interface type the node
81 Value type: Integer cells. A register entry, expressed
82 as a pair of cells, containing base and
84 Definition: the base address and size of the
85 corresponding interface programming
90 Parent node must be CCI interconnect node.
92 A CCI pmu node must contain the following properties:
97 Definition: Must contain one of:
100 "arm,cci-400-pmu" - DEPRECATED, permitted only where OS has
101 secure acces to CCI registers
104 Value type: Integer cells. A register entry, expressed
105 as a pair of cells, containing base and
107 Definition: the base address and size of the
108 corresponding interface programming
113 Value type: Integer cells. Array of interrupt specifier
114 entries, as defined in
115 ../interrupt-controller/interrupts.txt.
116 Definition: list of counter overflow interrupts, one per
117 counter. The interrupts must be specified
118 starting with the cycle counter overflow
119 interrupt, followed by counter0 overflow
120 interrupt, counter1 overflow interrupt,...
121 ,counterN overflow interrupt.
123 The CCI PMU has an interrupt signal for each
124 counter. The number of interrupts must be
125 equal to the number of counters.
127 * CCI interconnect bus masters
129 Description: masters in the device tree connected to a CCI port
130 (inclusive of CPUs and their cpu nodes).
132 A CCI interconnect bus master node must contain the following
137 Value type: <phandle>
138 Definition: a phandle containing the CCI control interface node
139 the master is connected to.
145 #address-cells = <1>;
149 compatible = "arm,cortex-a15";
150 cci-control-port = <&cci_control1>;
156 compatible = "arm,cortex-a15";
157 cci-control-port = <&cci_control1>;
163 compatible = "arm,cortex-a7";
164 cci-control-port = <&cci_control2>;
170 compatible = "arm,cortex-a7";
171 cci-control-port = <&cci_control2>;
178 compatible = "arm,pl330", "arm,primecell";
179 cci-control-port = <&cci_control0>;
180 reg = <0x0 0x3000000 0x0 0x1000>;
184 #dma-requests = <32>;
188 compatible = "arm,cci-400";
189 #address-cells = <1>;
191 reg = <0x0 0x2c090000 0 0x1000>;
192 ranges = <0x0 0x0 0x2c090000 0x10000>;
194 cci_control0: slave-if@1000 {
195 compatible = "arm,cci-400-ctrl-if";
196 interface-type = "ace-lite";
197 reg = <0x1000 0x1000>;
200 cci_control1: slave-if@4000 {
201 compatible = "arm,cci-400-ctrl-if";
202 interface-type = "ace";
203 reg = <0x4000 0x1000>;
206 cci_control2: slave-if@5000 {
207 compatible = "arm,cci-400-ctrl-if";
208 interface-type = "ace";
209 reg = <0x5000 0x1000>;
213 compatible = "arm,cci-400-pmu";
214 reg = <0x9000 0x5000>;
215 interrupts = <0 101 4>,
223 This CCI node corresponds to a CCI component whose control registers sits
224 at address 0x000000002c090000.
225 CCI slave interface @0x000000002c091000 is connected to dma controller dma0.
226 CCI slave interface @0x000000002c094000 is connected to CPUs {CPU0, CPU1};
227 CCI slave interface @0x000000002c095000 is connected to CPUs {CPU2, CPU3};