mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-05-02 00:20:05 +00:00
3ac3b6b0a3
The manifests describe the same hardware layout with only the secure partitions being different. Factor it out so it can be shared and only add the VM information separately. This has some deliberate side effects: the test configuration gets the full secure memory address space and drops the 0x7000000 region as that was accidentally copied over from the FVP platform and doesn't apply to TC. Also optee unconditionally gets the smaller mem_size as it's been working fine and simplifies the manifest. Small touch up is that mem_size-s are now in hex but otherwise the same number. Signed-off-by: Boyan Karatotev <boyan.karatotev@arm.com> Change-Id: Iea23f9769235eea32afa374952b9a0e4f6d3e9a1
41 lines
759 B
Text
41 lines
759 B
Text
/*
|
|
* Copyright (c) 2023-2024, Arm Limited. All rights reserved.
|
|
*
|
|
* SPDX-License-Identifier: BSD-3-Clause
|
|
*/
|
|
/dts-v1/;
|
|
|
|
#include <tc_spmc_manifest.dtsi>
|
|
|
|
/ {
|
|
hypervisor {
|
|
vm1 {
|
|
is_ffa_partition;
|
|
debug_name = "cactus-primary";
|
|
load_address = <0xfe000000>;
|
|
vcpu_count = <8>;
|
|
mem_size = <1048576>;
|
|
};
|
|
vm2 {
|
|
is_ffa_partition;
|
|
debug_name = "cactus-secondary";
|
|
load_address = <0xfe100000>;
|
|
vcpu_count = <8>;
|
|
mem_size = <1048576>;
|
|
};
|
|
vm3 {
|
|
is_ffa_partition;
|
|
debug_name = "cactus-tertiary";
|
|
load_address = <0xfe200000>;
|
|
vcpu_count = <1>;
|
|
mem_size = <1048576>;
|
|
};
|
|
vm4 {
|
|
is_ffa_partition;
|
|
debug_name = "ivy";
|
|
load_address = <0xfe600000>;
|
|
vcpu_count = <1>;
|
|
mem_size = <1048576>;
|
|
};
|
|
};
|
|
};
|