cci.txt 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172
  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 be set to
  26. "arm,cci-400"
  27. - reg
  28. Usage: required
  29. Value type: <prop-encoded-array>
  30. Definition: A standard property. Specifies base physical
  31. address of CCI control registers common to all
  32. interfaces.
  33. - ranges:
  34. Usage: required
  35. Value type: <prop-encoded-array>
  36. Definition: A standard property. Follow rules in the ePAPR for
  37. hierarchical bus addressing. CCI interfaces
  38. addresses refer to the parent node addressing
  39. scheme to declare their register bases.
  40. CCI interconnect node can define the following child nodes:
  41. - CCI control interface nodes
  42. Node name must be "slave-if".
  43. Parent node must be CCI interconnect node.
  44. A CCI control interface node must contain the following
  45. properties:
  46. - compatible
  47. Usage: required
  48. Value type: <string>
  49. Definition: must be set to
  50. "arm,cci-400-ctrl-if"
  51. - interface-type:
  52. Usage: required
  53. Value type: <string>
  54. Definition: must be set to one of {"ace", "ace-lite"}
  55. depending on the interface type the node
  56. represents.
  57. - reg:
  58. Usage: required
  59. Value type: <prop-encoded-array>
  60. Definition: the base address and size of the
  61. corresponding interface programming
  62. registers.
  63. * CCI interconnect bus masters
  64. Description: masters in the device tree connected to a CCI port
  65. (inclusive of CPUs and their cpu nodes).
  66. A CCI interconnect bus master node must contain the following
  67. properties:
  68. - cci-control-port:
  69. Usage: required
  70. Value type: <phandle>
  71. Definition: a phandle containing the CCI control interface node
  72. the master is connected to.
  73. Example:
  74. cpus {
  75. #size-cells = <0>;
  76. #address-cells = <1>;
  77. CPU0: cpu@0 {
  78. device_type = "cpu";
  79. compatible = "arm,cortex-a15";
  80. cci-control-port = <&cci_control1>;
  81. reg = <0x0>;
  82. };
  83. CPU1: cpu@1 {
  84. device_type = "cpu";
  85. compatible = "arm,cortex-a15";
  86. cci-control-port = <&cci_control1>;
  87. reg = <0x1>;
  88. };
  89. CPU2: cpu@100 {
  90. device_type = "cpu";
  91. compatible = "arm,cortex-a7";
  92. cci-control-port = <&cci_control2>;
  93. reg = <0x100>;
  94. };
  95. CPU3: cpu@101 {
  96. device_type = "cpu";
  97. compatible = "arm,cortex-a7";
  98. cci-control-port = <&cci_control2>;
  99. reg = <0x101>;
  100. };
  101. };
  102. dma0: dma@3000000 {
  103. compatible = "arm,pl330", "arm,primecell";
  104. cci-control-port = <&cci_control0>;
  105. reg = <0x0 0x3000000 0x0 0x1000>;
  106. interrupts = <10>;
  107. #dma-cells = <1>;
  108. #dma-channels = <8>;
  109. #dma-requests = <32>;
  110. };
  111. cci@2c090000 {
  112. compatible = "arm,cci-400";
  113. #address-cells = <1>;
  114. #size-cells = <1>;
  115. reg = <0x0 0x2c090000 0 0x1000>;
  116. ranges = <0x0 0x0 0x2c090000 0x6000>;
  117. cci_control0: slave-if@1000 {
  118. compatible = "arm,cci-400-ctrl-if";
  119. interface-type = "ace-lite";
  120. reg = <0x1000 0x1000>;
  121. };
  122. cci_control1: slave-if@4000 {
  123. compatible = "arm,cci-400-ctrl-if";
  124. interface-type = "ace";
  125. reg = <0x4000 0x1000>;
  126. };
  127. cci_control2: slave-if@5000 {
  128. compatible = "arm,cci-400-ctrl-if";
  129. interface-type = "ace";
  130. reg = <0x5000 0x1000>;
  131. };
  132. };
  133. This CCI node corresponds to a CCI component whose control registers sits
  134. at address 0x000000002c090000.
  135. CCI slave interface @0x000000002c091000 is connected to dma controller dma0.
  136. CCI slave interface @0x000000002c094000 is connected to CPUs {CPU0, CPU1};
  137. CCI slave interface @0x000000002c095000 is connected to CPUs {CPU2, CPU3};