Fix boot-order property in SP manifests
The FF-A binding specification [1] was recently updated to require all
integer properties, including boot-order, to be represented as 32-bit
wide values.
This commit updates the SP manifests accordingly to ensure compliance
with the updated specification.
Warning: this change may break compatibility with SPMC implementations.
In particular, the OP-TEE SPMC is affected and must be updated to a
compatible version.
Signed-off-by: Gyorgy Szing <gyorgy.szing@arm.com>
Change-Id: Iec2a6545924100d3e7cf0d7349fcba4025945ed2
diff --git a/deployments/spm-test2/opteesp/default_spm_test2.dts.in b/deployments/spm-test2/opteesp/default_spm_test2.dts.in
index 034fe22..48e7460 100644
--- a/deployments/spm-test2/opteesp/default_spm_test2.dts.in
+++ b/deployments/spm-test2/opteesp/default_spm_test2.dts.in
@@ -18,7 +18,7 @@
exception-level = <1>; /* S-EL0 */
execution-state = <0>; /* AARCH64 */
xlat-granule = <0>; /* 4KiB */
- boot-order = /bits/ 16 <@EXPORT_SP_BOOT_ORDER@>;
+ boot-order = <@EXPORT_SP_BOOT_ORDER@>;
messaging-method = <3>; /* Direct messaging only */
ns-interrupts-action = <2>; /* Non-secure interrupts are signaled */
elf-format = <1>;