vexpress.txt 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147
  1. ARM Versatile Express boards family
  2. -----------------------------------
  3. ARM's Versatile Express platform consists of a motherboard and one
  4. or more daughterboards (tiles). The motherboard provides a set of
  5. peripherals. Processor and RAM "live" on the tiles.
  6. The motherboard and each core tile should be described by a separate
  7. Device Tree source file, with the tile's description including
  8. the motherboard file using a /include/ directive. As the motherboard
  9. can be initialized in one of two different configurations ("memory
  10. maps"), care must be taken to include the correct one.
  11. Required properties in the root node:
  12. - compatible value:
  13. compatible = "arm,vexpress,<model>", "arm,vexpress";
  14. where <model> is the full tile model name (as used in the tile's
  15. Technical Reference Manual), eg.:
  16. - for Coretile Express A5x2 (V2P-CA5s):
  17. compatible = "arm,vexpress,v2p-ca5s", "arm,vexpress";
  18. - for Coretile Express A9x4 (V2P-CA9):
  19. compatible = "arm,vexpress,v2p-ca9", "arm,vexpress";
  20. If a tile comes in several variants or can be used in more then one
  21. configuration, the compatible value should be:
  22. compatible = "arm,vexpress,<model>,<variant>", \
  23. "arm,vexpress,<model>", "arm,vexpress";
  24. eg:
  25. - Coretile Express A15x2 (V2P-CA15) with Tech Chip 1:
  26. compatible = "arm,vexpress,v2p-ca15,tc1", \
  27. "arm,vexpress,v2p-ca15", "arm,vexpress";
  28. - LogicTile Express 13MG (V2F-2XV6) running Cortex-A7 (3 cores) SMM:
  29. compatible = "arm,vexpress,v2f-2xv6,ca7x3", \
  30. "arm,vexpress,v2f-2xv6", "arm,vexpress";
  31. Optional properties in the root node:
  32. - tile model name (use name from the tile's Technical Reference
  33. Manual, eg. "V2P-CA5s")
  34. model = "<model>";
  35. - tile's HBI number (unique ARM's board model ID, visible on the
  36. PCB's silkscreen) in hexadecimal transcription:
  37. arm,hbi = <0xhbi>
  38. eg:
  39. - for Coretile Express A5x2 (V2P-CA5s) HBI-0191:
  40. arm,hbi = <0x191>;
  41. - Coretile Express A9x4 (V2P-CA9) HBI-0225:
  42. arm,hbi = <0x225>;
  43. Top-level standard "cpus" node is required. It must contain a node
  44. with device_type = "cpu" property for every available core, eg.:
  45. cpus {
  46. #address-cells = <1>;
  47. #size-cells = <0>;
  48. cpu@0 {
  49. device_type = "cpu";
  50. compatible = "arm,cortex-a5";
  51. reg = <0>;
  52. };
  53. };
  54. The motherboard description file provides a single "motherboard" node
  55. using 2 address cells corresponding to the Static Memory Bus used
  56. between the motherboard and the tile. The first cell defines the Chip
  57. Select (CS) line number, the second cell address offset within the CS.
  58. All interrupt lines between the motherboard and the tile are active
  59. high and are described using single cell.
  60. Optional properties of the "motherboard" node:
  61. - motherboard's memory map variant:
  62. arm,v2m-memory-map = "<name>";
  63. where name is one of:
  64. - "rs1" - for RS1 map (i.a. peripherals on CS3); this map is also
  65. referred to as "ARM Cortex-A Series memory map":
  66. arm,v2m-memory-map = "rs1";
  67. When this property is missing, the motherboard is using the original
  68. memory map (also known as the "Legacy memory map", primarily used
  69. with the original CoreTile Express A9x4) with peripherals on CS7.
  70. Motherboard .dtsi files provide a set of labelled peripherals that
  71. can be used to obtain required phandle in the tile's "aliases" node:
  72. - UARTs, note that the numbers correspond to the physical connectors
  73. on the motherboard's back panel:
  74. v2m_serial0, v2m_serial1, v2m_serial2 and v2m_serial3
  75. - I2C controllers:
  76. v2m_i2c_dvi and v2m_i2c_pcie
  77. - SP804 timers:
  78. v2m_timer01 and v2m_timer23
  79. Current Linux implementation requires a "arm,v2m_timer" alias
  80. pointing at one of the motherboard's SP804 timers, if it is to be
  81. used as the system timer. This alias should be defined in the
  82. motherboard files.
  83. The tile description must define "ranges", "interrupt-map-mask" and
  84. "interrupt-map" properties to translate the motherboard's address
  85. and interrupt space into one used by the tile's processor.
  86. Abbreviated example:
  87. /dts-v1/;
  88. / {
  89. model = "V2P-CA5s";
  90. arm,hbi = <0x225>;
  91. compatible = "arm,vexpress-v2p-ca5s", "arm,vexpress";
  92. interrupt-parent = <&gic>;
  93. #address-cells = <1>;
  94. #size-cells = <1>;
  95. chosen { };
  96. aliases {
  97. serial0 = &v2m_serial0;
  98. };
  99. cpus {
  100. #address-cells = <1>;
  101. #size-cells = <0>;
  102. cpu@0 {
  103. device_type = "cpu";
  104. compatible = "arm,cortex-a5";
  105. reg = <0>;
  106. };
  107. };
  108. gic: interrupt-controller@2c001000 {
  109. compatible = "arm,cortex-a9-gic";
  110. #interrupt-cells = <3>;
  111. #address-cells = <0>;
  112. interrupt-controller;
  113. reg = <0x2c001000 0x1000>,
  114. <0x2c000100 0x100>;
  115. };
  116. motherboard {
  117. /* CS0 is visible at 0x08000000 */
  118. ranges = <0 0 0x08000000 0x04000000>;
  119. interrupt-map-mask = <0 0 63>;
  120. /* Active high IRQ 0 is connected to GIC's SPI0 */
  121. interrupt-map = <0 0 0 &gic 0 0 4>;
  122. };
  123. };
  124. /include/ "vexpress-v2m-rs1.dtsi"