cci.txt 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232
  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. "arm,cci-550"
  29. - reg
  30. Usage: required
  31. Value type: Integer cells. A register entry, expressed as a pair
  32. of cells, containing base and size.
  33. Definition: A standard property. Specifies base physical
  34. address of CCI control registers common to all
  35. interfaces.
  36. - ranges:
  37. Usage: required
  38. Value type: Integer cells. An array of range entries, expressed
  39. as a tuple of cells, containing child address,
  40. parent address and the size of the region in the
  41. child address space.
  42. Definition: A standard property. Follow rules in the ePAPR for
  43. hierarchical bus addressing. CCI interfaces
  44. addresses refer to the parent node addressing
  45. scheme to declare their register bases.
  46. CCI interconnect node can define the following child nodes:
  47. - CCI control interface nodes
  48. Node name must be "slave-if".
  49. Parent node must be CCI interconnect node.
  50. A CCI control interface node must contain the following
  51. properties:
  52. - compatible
  53. Usage: required
  54. Value type: <string>
  55. Definition: must be set to
  56. "arm,cci-400-ctrl-if"
  57. - interface-type:
  58. Usage: required
  59. Value type: <string>
  60. Definition: must be set to one of {"ace", "ace-lite"}
  61. depending on the interface type the node
  62. represents.
  63. - reg:
  64. Usage: required
  65. Value type: Integer cells. A register entry, expressed
  66. as a pair of cells, containing base and
  67. size.
  68. Definition: the base address and size of the
  69. corresponding interface programming
  70. registers.
  71. - CCI PMU node
  72. Parent node must be CCI interconnect node.
  73. A CCI pmu node must contain the following properties:
  74. - compatible
  75. Usage: required
  76. Value type: <string>
  77. Definition: Must contain one of:
  78. "arm,cci-400-pmu,r0"
  79. "arm,cci-400-pmu,r1"
  80. "arm,cci-400-pmu" - DEPRECATED, permitted only where OS has
  81. secure access to CCI registers
  82. "arm,cci-500-pmu,r0"
  83. "arm,cci-550-pmu,r0"
  84. - reg:
  85. Usage: required
  86. Value type: Integer cells. A register entry, expressed
  87. as a pair of cells, containing base and
  88. size.
  89. Definition: the base address and size of the
  90. corresponding interface programming
  91. registers.
  92. - interrupts:
  93. Usage: required
  94. Value type: Integer cells. Array of interrupt specifier
  95. entries, as defined in
  96. ../interrupt-controller/interrupts.txt.
  97. Definition: list of counter overflow interrupts, one per
  98. counter. The interrupts must be specified
  99. starting with the cycle counter overflow
  100. interrupt, followed by counter0 overflow
  101. interrupt, counter1 overflow interrupt,...
  102. ,counterN overflow interrupt.
  103. The CCI PMU has an interrupt signal for each
  104. counter. The number of interrupts must be
  105. equal to the number of counters.
  106. * CCI interconnect bus masters
  107. Description: masters in the device tree connected to a CCI port
  108. (inclusive of CPUs and their cpu nodes).
  109. A CCI interconnect bus master node must contain the following
  110. properties:
  111. - cci-control-port:
  112. Usage: required
  113. Value type: <phandle>
  114. Definition: a phandle containing the CCI control interface node
  115. the master is connected to.
  116. Example:
  117. cpus {
  118. #size-cells = <0>;
  119. #address-cells = <1>;
  120. CPU0: cpu@0 {
  121. device_type = "cpu";
  122. compatible = "arm,cortex-a15";
  123. cci-control-port = <&cci_control1>;
  124. reg = <0x0>;
  125. };
  126. CPU1: cpu@1 {
  127. device_type = "cpu";
  128. compatible = "arm,cortex-a15";
  129. cci-control-port = <&cci_control1>;
  130. reg = <0x1>;
  131. };
  132. CPU2: cpu@100 {
  133. device_type = "cpu";
  134. compatible = "arm,cortex-a7";
  135. cci-control-port = <&cci_control2>;
  136. reg = <0x100>;
  137. };
  138. CPU3: cpu@101 {
  139. device_type = "cpu";
  140. compatible = "arm,cortex-a7";
  141. cci-control-port = <&cci_control2>;
  142. reg = <0x101>;
  143. };
  144. };
  145. dma0: dma@3000000 {
  146. compatible = "arm,pl330", "arm,primecell";
  147. cci-control-port = <&cci_control0>;
  148. reg = <0x0 0x3000000 0x0 0x1000>;
  149. interrupts = <10>;
  150. #dma-cells = <1>;
  151. #dma-channels = <8>;
  152. #dma-requests = <32>;
  153. };
  154. cci@2c090000 {
  155. compatible = "arm,cci-400";
  156. #address-cells = <1>;
  157. #size-cells = <1>;
  158. reg = <0x0 0x2c090000 0 0x1000>;
  159. ranges = <0x0 0x0 0x2c090000 0x10000>;
  160. cci_control0: slave-if@1000 {
  161. compatible = "arm,cci-400-ctrl-if";
  162. interface-type = "ace-lite";
  163. reg = <0x1000 0x1000>;
  164. };
  165. cci_control1: slave-if@4000 {
  166. compatible = "arm,cci-400-ctrl-if";
  167. interface-type = "ace";
  168. reg = <0x4000 0x1000>;
  169. };
  170. cci_control2: slave-if@5000 {
  171. compatible = "arm,cci-400-ctrl-if";
  172. interface-type = "ace";
  173. reg = <0x5000 0x1000>;
  174. };
  175. pmu@9000 {
  176. compatible = "arm,cci-400-pmu";
  177. reg = <0x9000 0x5000>;
  178. interrupts = <0 101 4>,
  179. <0 102 4>,
  180. <0 103 4>,
  181. <0 104 4>,
  182. <0 105 4>;
  183. };
  184. };
  185. This CCI node corresponds to a CCI component whose control registers sits
  186. at address 0x000000002c090000.
  187. CCI slave interface @0x000000002c091000 is connected to dma controller dma0.
  188. CCI slave interface @0x000000002c094000 is connected to CPUs {CPU0, CPU1};
  189. CCI slave interface @0x000000002c095000 is connected to CPUs {CPU2, CPU3};