blob: c7581394c2c064ab354b9c55a22b77e9071542b4 [file] [log] [blame]
Olivier Deprezcbf7d5b2023-05-22 12:12:24 +02001FF-A manifest binding to device tree
2====================================
3
4This document defines the nodes and properties used to define a partition,
5according to the FF-A specification.
6
7.. contents::
8
9Partition Properties
10--------------------
11
12- compatible [mandatory]
13 - value type: <string>
14 - Must be the string "arm,ffa-manifest-X.Y" which specifies the major and
15 minor versions of the device tree binding for the FFA manifest represented
16 by this node. The minor number is incremented if the binding changes in a
17 backwards compatible manner.
18
19 - X is an integer representing the major version number of this document.
20 - Y is an integer representing the minor version number of this document.
21
22- ffa-version [mandatory]
23 - value type: <u32>
24 - Must be two 16 bits values (X, Y), concatenated as 31:16 -> X,
25 15:0 -> Y, where:
26
27 - X is the major version of FF-A expected by the partition at the FFA
28 instance it will execute.
29 - Y is the minor version of FF-A expected by the partition at the FFA
30 instance it will execute.
31
32- uuid [mandatory]
33 - value type: <prop-encoded-array>
34 - An array consisting of 4 <u32> values, identifying the UUID of the service
35 implemented by this partition. The UUID format is described in RFC 4122.
36
37- id
38 - value type: <u32>
39 - Pre-allocated partition ID.
40
41- auxiliary-id
42 - value type: <u32>
43 - Pre-allocated ID that could be used in memory management transactions.
44
45- description
46 - value type: <string>
47 - Name of the partition e.g. for debugging purposes.
48
49- execution-ctx-count [mandatory]
50 - value type: <u32>
51 - Number of vCPUs that a VM or SP wants to instantiate.
52
53 - In the absence of virtualization, this is the number of execution
54 contexts that a partition implements.
55 - If value of this field = 1 and number of PEs > 1 then the partition is
56 treated as UP & migrate capable.
57 - If the value of this field > 1 then the partition is treated as a MP
58 capable partition irrespective of the number of PEs.
59
60- exception-level [mandatory]
61 - value type: <u32>
62 - The target exception level for the partition:
63
64 - 0x0: EL1
65 - 0x1: S_EL0
66 - 0x2: S_EL1
67
68- execution-state [mandatory]
69 - value type: <u32>
70 - The target execution state of the partition:
71
72 - 0: AArch64
73 - 1: AArch32
74
75- load-address
76 - value type: <u64>
77 - Physical base address of the partition in memory. Absence of this field
78 indicates that the partition is position independent and can be loaded at
79 any address chosen at boot time.
80
81- entrypoint-offset
82 - value type: <u64>
83 - Offset from the base of the partition's binary image to the entry point of
84 the partition. Absence of this field indicates that the entry point is at
85 offset 0x0 from the base of the partition's binary.
86
87- xlat-granule [mandatory]
88 - value type: <u32>
89 - Translation granule used with the partition:
90
91 - 0x0: 4k
92 - 0x1: 16k
93 - 0x2: 64k
94
95- boot-order
96 - value type: <u16>
97 - A unique number amongst all partitions that specifies if this partition
98 must be booted before others. The partition with the smaller number will be
99 booted first.
100
101- rx-tx-buffer
102 - value type: "memory-regions" node
103 - Specific "memory-regions" nodes that describe the RX/TX buffers expected
104 by the partition.
105 The "compatible" must be the string "arm,ffa-manifest-rx_tx-buffer".
106
107- messaging-method [mandatory]
108 - value type: <u8>
109 - Specifies which messaging methods are supported by the partition, set bit
110 means the feature is supported, clear bit - not supported:
111
112 - Bit[0]: partition can receive direct requests if set
113 - Bit[1]: partition can send direct requests if set
114 - Bit[2]: partition can send and receive indirect messages
115
116- managed-exit
117 - value type: <empty>
118 - Specifies if managed exit is supported.
119 - This field is deprecated in favor of ns-interrupts-action field in the FF-A
120 v1.1 EAC0 spec.
121
Madhukar Pappireddyddef7d72023-10-10 18:06:16 -0500122- managed-exit-virq
123 - value type: <empty>
124 - Indicates if the partition needs managed exit, if supported, to be signaled
125 through vFIQ signal.
126
Olivier Deprezcbf7d5b2023-05-22 12:12:24 +0200127- ns-interrupts-action [mandatory]
128 - value type: <u32>
129 - Specifies the action that the SPMC must take in response to a Non-secure
130 physical interrupt.
131
132 - 0x0: Non-secure interrupt is queued
133 - 0x1: Non-secure interrupt is signaled after a managed exit
134 - 0x2: Non-secure interrupt is signaled
135
136 - This field supersedes the managed-exit field in the FF-A v1.0 spec.
137
138- other-s-interrupts-action
139 - value type: <u32>
140 - Specifies the action that the SPMC must take in response to a Other-Secure
141 physical interrupt.
142
143 - 0x0: Other-Secure interrupt is queued
144 - 0x1: Other-Secure interrupt is signaled
145
Madhukar Pappireddyddef7d72023-10-10 18:06:16 -0500146- runtime-model
147 - value type: <u32>
148 - Indicates whether the SP execution can be preempted.
149 - This field is deprecated in favor of other-s-interrupts-action and
150 ns-interrupts-action fields in the FF-A v1.1 spec.
151
Olivier Deprezcbf7d5b2023-05-22 12:12:24 +0200152- has-primary-scheduler
153 - value type: <empty>
154 - Presence of this field indicates that the partition implements the primary
155 scheduler. If so, run-time EL must be EL1.
156
157- time-slice-mem
158 - value type: <empty>
159 - Presence of this field indicates that the partition doesn't expect the
160 partition manager to time slice long running memory management functions.
161
162- gp-register-num
163 - value type: <u32>
164 - The field specifies the general purpose register number but not its width.
165 The width is derived from the partition's execution state, as specified in
166 the partition properties. For example, if the number value is 1 then the
167 general-purpose register used will be x1 in AArch64 state and w1 in AArch32
168 state.
169 Presence of this field indicates that the partition expects the address of
170 the FF-A boot information blob to be passed in the specified general purpose
171 register.
172
Olivier Deprezcbf7d5b2023-05-22 12:12:24 +0200173- power-management-messages
174 - value type: <u32>
175 - Specifies which power management messages a partition subscribes to.
176 A set bit means the partition should be informed of the power event, clear
177 bit - should not be informed of event:
178
179 - Bit[0]: CPU_OFF
180 - Bit[1]: CPU_SUSPEND
181 - Bit[2]: CPU_SUSPEND_RESUME
182
183Memory Regions
184--------------
185
186- compatible [mandatory]
187 - value type: <string>
188 - Must be the string "arm,ffa-manifest-memory-regions".
189
190- description
191 - value type: <string>
192 - Name of the memory region e.g. for debugging purposes.
193
194- pages-count [mandatory]
195 - value type: <u32>
196 - Count of pages of memory region as a multiple of the translation granule
197 size
198
199- attributes [mandatory]
200 - value type: <u32>
201 - Mapping modes: ORed to get required permission
202
203 - 0x1: Read
204 - 0x2: Write
205 - 0x4: Execute
206 - 0x8: Security state
207
208- base-address
209 - value type: <u64>
210 - Base address of the region. The address must be aligned to the translation
211 granule size.
212 The address given may be a Physical Address (PA), Virtual Address (VA), or
213 Intermediate Physical Address (IPA). Refer to the FF-A specification for
214 more information on the restrictions around the address type.
215 If the base address is omitted then the partition manager must map a memory
216 region of the specified size into the partition's translation regime and
217 then communicate the region properties (including the base address chosen
218 by the partition manager) to the partition.
219
220Device Regions
221--------------
222
223- compatible [mandatory]
224 - value type: <string>
225 - Must be the string "arm,ffa-manifest-device-regions".
226
227- description
228 - value type: <string>
229 - Name of the device region e.g. for debugging purposes.
230
231- pages-count [mandatory]
232 - value type: <u32>
233 - Count of pages of memory region as a multiple of the translation granule
234 size
235
236- attributes [mandatory]
237 - value type: <u32>
238 - Mapping modes: ORed to get required permission
239
240 - 0x1: Read
241 - 0x2: Write
242 - 0x4: Execute
243 - 0x8: Security state
244
245- base-address [mandatory]
246 - value type: <u64>
247 - Base address of the region. The address must be aligned to the translation
248 granule size.
249 The address given may be a Physical Address (PA), Virtual Address (VA), or
250 Intermediate Physical Address (IPA). Refer to the FF-A specification for
251 more information on the restrictions around the address type.
252
253- smmu-id
254 - value type: <u32>
255 - On systems with multiple System Memory Management Units (SMMUs) this
256 identifier is used to inform the partition manager which SMMU the device is
257 upstream of. If the field is omitted then it is assumed that the device is
258 not upstream of any SMMU.
259
260- stream-ids
261 - value type: <prop-encoded-array>
Madhukar Pappireddyddef7d72023-10-10 18:06:16 -0500262 - List of IDs where an ID is a unique <u32> value amongst all devices assigned
263 to the partition.
Olivier Deprezcbf7d5b2023-05-22 12:12:24 +0200264
265- interrupts [mandatory]
266 - value type: <prop-encoded-array>
267 - A list of (id, attributes) pair describing the device interrupts, where:
268
269 - id: The <u32> interrupt IDs.
270 - attributes: A <u32> value, containing attributes for each interrupt ID:
271
272 +----------------------+----------+
273 |Field | Bit(s) |
274 +----------------------+----------+
275 | Priority | 7:0 |
276 +----------------------+----------+
277 | Security state | 8 |
278 +----------------------+----------+
279 | Config(Edge/Level) | 9 |
280 +----------------------+----------+
281 | Type(SPI/PPI/SGI) | 11:10 |
282 +----------------------+----------+
283
284 Security state:
285 - Secure: 1
286 - Non-secure: 0
287
288 Configuration:
289 - Edge triggered: 0
290 - Level triggered: 1
291
292 Type:
293 - SPI: 0b10
294 - PPI: 0b01
295 - SGI: 0b00
296
297- interrupts-target
298 - value type: <prop-encoded-array>
299 - A list of (id, mpdir upper bits, mpidr lower bits) tuples describing which
300 mpidr the interrupt is routed to, where:
301
302 - id: The <u32> interrupt ID. Must be one of those specified in the
303 "interrupts" field.
304 - mpidr upper bits: The <u32> describing the upper bits of the 64 bits
305 mpidr
306 - mpidr lower bits: The <u32> describing the lower bits of the 64 bits
307 mpidr
308
309- exclusive-access
310 - value type: <empty>
311 - Presence of this field implies that this endpoint must be granted exclusive
312 access and ownership of this device's MMIO region.
313
314--------------
315
316*Copyright (c) 2019-2023, Arm Limited and Contributors. All rights reserved.*