xref: /linux/Documentation/devicetree/bindings/arm/arm,vexpress-juno.yaml (revision a1c3be890440a1769ed6f822376a3e3ab0d42994) 
1# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2%YAML 1.2
3---
4$id: http://devicetree.org/schemas/arm/arm,vexpress-juno.yaml#
5$schema: http://devicetree.org/meta-schemas/core.yaml#
6
7title: ARM Versatile Express and Juno Boards Device Tree Bindings
8
9maintainers:
10  - Sudeep Holla <sudeep.holla@arm.com>
11  - Linus Walleij <linus.walleij@linaro.org>
12
13description: |+
14  ARM's Versatile Express platform were built as reference designs for exploring
15  multicore Cortex-A class systems. The Versatile Express family contains both
16  32 bit (Aarch32) and 64 bit (Aarch64) systems.
17
18  The board consist of a motherboard and one or more daughterboards (tiles). The
19  motherboard provides a set of peripherals. Processor and RAM "live" on the
20  tiles.
21
22  The motherboard and each core tile should be described by a separate Device
23  Tree source file, with the tile's description including the motherboard file
24  using an include directive. As the motherboard can be initialized in one of
25  two different configurations ("memory maps"), care must be taken to include
26  the correct one.
27
28  When a new generation of boards were introduced under the name "Juno", these
29  shared to many common characteristics with the Versatile Express that the
30  "arm,vexpress" compatible was retained in the root node, and these are
31  included in this binding schema as well.
32
33  The root node indicates the CPU SoC on the core tile, and this
34  is a daughterboard to the main motherboard. The name used in the compatible
35  string shall match the name given in the core tile's technical reference
36  manual, followed by "arm,vexpress" as an additional compatible value. If
37  further subvariants are released of the core tile, even more fine-granular
38  compatible strings with up to three compatible strings are used.
39
40properties:
41  $nodename:
42    const: '/'
43  compatible:
44    oneOf:
45      - description: CoreTile Express A9x4 (V2P-CA9) has 4 Cortex A9 CPU cores
46          in MPCore configuration in a test chip on the core tile. See ARM
47          DUI 0448I. This was the first Versatile Express platform.
48        items:
49          - const: arm,vexpress,v2p-ca9
50          - const: arm,vexpress
51      - description: CoreTile Express A5x2 (V2P-CA5s) has 2 Cortex A5 CPU cores
52          in a test chip on the core tile. It is intended to evaluate NEON, FPU
53          and Jazelle support in the Cortex A5 family. See ARM DUI 0541C.
54        items:
55          - const: arm,vexpress,v2p-ca5s
56          - const: arm,vexpress
57      - description: Coretile Express A15x2 (V2P-CA15) has 2 Cortex A15 CPU
58          cores in a MPCore configuration in a test chip on the core tile. See
59          ARM DUI 0604F.
60        items:
61          - const: arm,vexpress,v2p-ca15
62          - const: arm,vexpress
63      - description: CoreTile Express A15x4 (V2P-CA15, HBI-0237A) has 4 Cortex
64          A15 CPU cores in a test chip on the core tile. This is the first test
65          chip called "TC1".
66        items:
67          - const: arm,vexpress,v2p-ca15,tc1
68          - const: arm,vexpress,v2p-ca15
69          - const: arm,vexpress
70      - description: Coretile Express A15x2 A7x3 (V2P-CA15_A7) has 2 Cortex A15
71          CPU cores and 3 Cortex A7 cores in a big.LITTLE MPCore configuration
72          in a test chip on the core tile. See ARM DDI 0503I.
73        items:
74          - const: arm,vexpress,v2p-ca15_a7
75          - const: arm,vexpress
76      - description: LogicTile Express 20MG (V2F-1XV7) has 2 Cortex A53 CPU
77          cores in a test chip on the core tile. See ARM DDI 0498D.
78        items:
79          - const: arm,vexpress,v2f-1xv7,ca53x2
80          - const: arm,vexpress,v2f-1xv7
81          - const: arm,vexpress
82      - description: Arm Versatile Express Juno "r0" (the first Juno board,
83          V2M-Juno) was introduced as a vehicle for evaluating big.LITTLE on
84          AArch64 CPU cores. It has 2 Cortex A57 CPU cores and 4 Cortex A53
85          cores in a big.LITTLE configuration. It also features the MALI T624
86          GPU. See ARM document 100113_0000_07_en.
87        items:
88          - const: arm,juno
89          - const: arm,vexpress
90      - description: Arm Versatile Express Juno r1 Development Platform
91          (V2M-Juno r1) was introduced mainly aimed at development of PCIe
92          based systems. Juno r1 also has support for AXI masters placed on
93          the TLX connectors to join the coherency domain. Otherwise it is the
94          same configuration as Juno r0. See ARM document 100122_0100_06_en.
95        items:
96          - const: arm,juno-r1
97          - const: arm,juno
98          - const: arm,vexpress
99      - description: Arm Versatile Express Juno r2 Development Platform
100          (V2M-Juno r2). It has the same feature set as Juno r0 and r1. See
101          ARM document 100114_0200_04_en.
102        items:
103          - const: arm,juno-r2
104          - const: arm,juno
105          - const: arm,vexpress
106      - description: Arm AEMv8a Versatile Express Real-Time System Model
107          (VE RTSM) is a programmers view of the Versatile Express with Arm
108          v8A hardware. See ARM DUI 0575D.
109        items:
110          - const: arm,rtsm_ve,aemv8a
111          - const: arm,vexpress
112      - description: Arm FVP (Fixed Virtual Platform) base model revision C
113          See ARM Document 100964_1190_00_en.
114        items:
115          - const: arm,fvp-base-revc
116          - const: arm,vexpress
117      - description: Arm Foundation model for Aarch64
118        items:
119          - const: arm,foundation-aarch64
120          - const: arm,vexpress
121
122  arm,hbi:
123    $ref: '/schemas/types.yaml#/definitions/uint32'
124    description: This indicates the ARM HBI (Hardware Board ID), this is
125      ARM's unique board model ID, visible on the PCB's silkscreen.
126
127  arm,vexpress,site:
128    description: As Versatile Express can be configured in number of physically
129      different setups, the device tree should describe platform topology.
130      For this reason the root node and main motherboard node must define this
131      property, describing the physical location of the children nodes.
132      0 means motherboard site, while 1 and 2 are daughterboard sites, and
133      0xf means "sisterboard" which is the site containing the main CPU tile.
134    $ref: '/schemas/types.yaml#/definitions/uint32'
135    minimum: 0
136    maximum: 15
137
138  arm,vexpress,position:
139    description: When daughterboards are stacked on one site, their position
140      in the stack be be described this attribute.
141    $ref: '/schemas/types.yaml#/definitions/uint32'
142    minimum: 0
143    maximum: 3
144
145  arm,vexpress,dcc:
146    description: When describing tiles consisting of more than one DCC, its
147      number can be specified with this attribute.
148    $ref: '/schemas/types.yaml#/definitions/uint32'
149    minimum: 0
150    maximum: 3
151
152patternProperties:
153  "^bus@[0-9a-f]+$":
154    description: Static Memory Bus (SMB) node, if this exists it describes
155      the connection between the motherboard and any tiles. Sometimes the
156      compatible is placed directly under this node, sometimes it is placed
157      in a subnode named "motherboard". Sometimes the compatible includes
158      "arm,vexpress,v2?-p1" sometimes (on software models) is is just
159      "simple-bus". If the compatible is placed in the "motherboard" node,
160      it is stricter and always has two compatibles.
161    type: object
162    $ref: '/schemas/simple-bus.yaml'
163
164    properties:
165      compatible:
166        oneOf:
167          - items:
168              - enum:
169                  - arm,vexpress,v2m-p1
170                  - arm,vexpress,v2p-p1
171              - const: simple-bus
172          - const: simple-bus
173      motherboard:
174        type: object
175        description: The motherboard description provides a single "motherboard"
176          node using 2 address cells corresponding to the Static Memory Bus
177          used between the motherboard and the tile. The first cell defines the
178          Chip Select (CS) line number, the second cell address offset within
179          the CS. All interrupt lines between the motherboard and the tile
180          are active high and are described using single cell.
181        properties:
182          "#address-cells":
183            const: 2
184          "#size-cells":
185            const: 1
186          compatible:
187            items:
188              - enum:
189                  - arm,vexpress,v2m-p1
190                  - arm,vexpress,v2p-p1
191              - const: simple-bus
192          arm,v2m-memory-map:
193            description: This describes the memory map type.
194            $ref: '/schemas/types.yaml#/definitions/string'
195            enum:
196              - rs1
197              - rs2
198
199        required:
200          - compatible
201    required:
202      - compatible
203
204allOf:
205  - if:
206      properties:
207        compatible:
208          contains:
209            enum:
210              - arm,vexpress,v2p-ca9
211              - arm,vexpress,v2p-ca5s
212              - arm,vexpress,v2p-ca15
213              - arm,vexpress,v2p-ca15_a7
214              - arm,vexpress,v2f-1xv7,ca53x2
215    then:
216      required:
217        - arm,hbi
218
219additionalProperties: true
220
221...
222