cci.txt 6.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230
  1. =======================================================
  2. ARM CCI cache coherent interconnect binding description
  3. =======================================================
  4. ARM multi-cluster systems maintain intra-cluster coherency through a
  5. cache coherent interconnect (CCI) that is capable of monitoring bus
  6. transactions and manage coherency, TLB invalidations and memory barriers.
  7. It allows snooping and distributed virtual memory message broadcast across
  8. clusters, through memory mapped interface, with a global control register
  9. space and multiple sets of interface control registers, one per slave
  10. interface.
  11. Bindings for the CCI node follow the ePAPR standard, available from:
  12. www.power.org/documentation/epapr-version-1-1/
  13. with the addition of the bindings described in this document which are
  14. specific to ARM.
  15. * CCI interconnect node
  16. Description: Describes a CCI cache coherent Interconnect component
  17. Node name must be "cci".
  18. Node's parent must be the root node /, and the address space visible
  19. through the CCI interconnect is the same as the one seen from the
  20. root node (ie from CPUs perspective as per DT standard).
  21. Every CCI node has to define the following properties:
  22. - compatible
  23. Usage: required
  24. Value type: <string>
  25. Definition: must contain one of the following:
  26. "arm,cci-400"
  27. "arm,cci-500"
  28. - reg
  29. Usage: required
  30. Value type: Integer cells. A register entry, expressed as a pair
  31. of cells, containing base and size.
  32. Definition: A standard property. Specifies base physical
  33. address of CCI control registers common to all
  34. interfaces.
  35. - ranges:
  36. Usage: required
  37. Value type: Integer cells. An array of range entries, expressed
  38. as a tuple of cells, containing child address,
  39. parent address and the size of the region in the
  40. child address space.
  41. Definition: A standard property. Follow rules in the ePAPR for
  42. hierarchical bus addressing. CCI interfaces
  43. addresses refer to the parent node addressing
  44. scheme to declare their register bases.
  45. CCI interconnect node can define the following child nodes:
  46. - CCI control interface nodes
  47. Node name must be "slave-if".
  48. Parent node must be CCI interconnect node.
  49. A CCI control interface node must contain the following
  50. properties:
  51. - compatible
  52. Usage: required
  53. Value type: <string>
  54. Definition: must be set to
  55. "arm,cci-400-ctrl-if"
  56. - interface-type:
  57. Usage: required
  58. Value type: <string>
  59. Definition: must be set to one of {"ace", "ace-lite"}
  60. depending on the interface type the node
  61. represents.
  62. - reg:
  63. Usage: required
  64. Value type: Integer cells. A register entry, expressed
  65. as a pair of cells, containing base and
  66. size.
  67. Definition: the base address and size of the
  68. corresponding interface programming
  69. registers.
  70. - CCI PMU node
  71. Parent node must be CCI interconnect node.
  72. A CCI pmu node must contain the following properties:
  73. - compatible
  74. Usage: required
  75. Value type: <string>
  76. Definition: Must contain one of:
  77. "arm,cci-400-pmu,r0"
  78. "arm,cci-400-pmu,r1"
  79. "arm,cci-400-pmu" - DEPRECATED, permitted only where OS has
  80. secure acces to CCI registers
  81. "arm,cci-500-pmu,r0"
  82. - reg:
  83. Usage: required
  84. Value type: Integer cells. A register entry, expressed
  85. as a pair of cells, containing base and
  86. size.
  87. Definition: the base address and size of the
  88. corresponding interface programming
  89. registers.
  90. - interrupts:
  91. Usage: required
  92. Value type: Integer cells. Array of interrupt specifier
  93. entries, as defined in
  94. ../interrupt-controller/interrupts.txt.
  95. Definition: list of counter overflow interrupts, one per
  96. counter. The interrupts must be specified
  97. starting with the cycle counter overflow
  98. interrupt, followed by counter0 overflow
  99. interrupt, counter1 overflow interrupt,...
  100. ,counterN overflow interrupt.
  101. The CCI PMU has an interrupt signal for each
  102. counter. The number of interrupts must be
  103. equal to the number of counters.
  104. * CCI interconnect bus masters
  105. Description: masters in the device tree connected to a CCI port
  106. (inclusive of CPUs and their cpu nodes).
  107. A CCI interconnect bus master node must contain the following
  108. properties:
  109. - cci-control-port:
  110. Usage: required
  111. Value type: <phandle>
  112. Definition: a phandle containing the CCI control interface node
  113. the master is connected to.
  114. Example:
  115. cpus {
  116. #size-cells = <0>;
  117. #address-cells = <1>;
  118. CPU0: cpu@0 {
  119. device_type = "cpu";
  120. compatible = "arm,cortex-a15";
  121. cci-control-port = <&cci_control1>;
  122. reg = <0x0>;
  123. };
  124. CPU1: cpu@1 {
  125. device_type = "cpu";
  126. compatible = "arm,cortex-a15";
  127. cci-control-port = <&cci_control1>;
  128. reg = <0x1>;
  129. };
  130. CPU2: cpu@100 {
  131. device_type = "cpu";
  132. compatible = "arm,cortex-a7";
  133. cci-control-port = <&cci_control2>;
  134. reg = <0x100>;
  135. };
  136. CPU3: cpu@101 {
  137. device_type = "cpu";
  138. compatible = "arm,cortex-a7";
  139. cci-control-port = <&cci_control2>;
  140. reg = <0x101>;
  141. };
  142. };
  143. dma0: dma@3000000 {
  144. compatible = "arm,pl330", "arm,primecell";
  145. cci-control-port = <&cci_control0>;
  146. reg = <0x0 0x3000000 0x0 0x1000>;
  147. interrupts = <10>;
  148. #dma-cells = <1>;
  149. #dma-channels = <8>;
  150. #dma-requests = <32>;
  151. };
  152. cci@2c090000 {
  153. compatible = "arm,cci-400";
  154. #address-cells = <1>;
  155. #size-cells = <1>;
  156. reg = <0x0 0x2c090000 0 0x1000>;
  157. ranges = <0x0 0x0 0x2c090000 0x10000>;
  158. cci_control0: slave-if@1000 {
  159. compatible = "arm,cci-400-ctrl-if";
  160. interface-type = "ace-lite";
  161. reg = <0x1000 0x1000>;
  162. };
  163. cci_control1: slave-if@4000 {
  164. compatible = "arm,cci-400-ctrl-if";
  165. interface-type = "ace";
  166. reg = <0x4000 0x1000>;
  167. };
  168. cci_control2: slave-if@5000 {
  169. compatible = "arm,cci-400-ctrl-if";
  170. interface-type = "ace";
  171. reg = <0x5000 0x1000>;
  172. };
  173. pmu@9000 {
  174. compatible = "arm,cci-400-pmu";
  175. reg = <0x9000 0x5000>;
  176. interrupts = <0 101 4>,
  177. <0 102 4>,
  178. <0 103 4>,
  179. <0 104 4>,
  180. <0 105 4>;
  181. };
  182. };
  183. This CCI node corresponds to a CCI component whose control registers sits
  184. at address 0x000000002c090000.
  185. CCI slave interface @0x000000002c091000 is connected to dma controller dma0.
  186. CCI slave interface @0x000000002c094000 is connected to CPUs {CPU0, CPU1};
  187. CCI slave interface @0x000000002c095000 is connected to CPUs {CPU2, CPU3};