| Message ID | 20250910090346.1623394-2-ross.burton@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | [1/3] CI: no need to configure coresight explicitly | expand |
diff --git a/meta-arm-bsp/conf/machine/corstone1000-mps3.conf b/meta-arm-bsp/conf/machine/corstone1000-mps3.conf index 88d01b096f..cefe184bf7 100644 --- a/meta-arm-bsp/conf/machine/corstone1000-mps3.conf +++ b/meta-arm-bsp/conf/machine/corstone1000-mps3.conf @@ -9,3 +9,6 @@ TFA_TARGET_PLATFORM = "fpga" PLATFORM_IS_FVP = "FALSE" TS_PLATFORM = "arm/corstone1000-mps3" + +# Unlike the FVP, MPS3 supports CoreSight +MACHINE_FEATURES += "coresight"
The Corstone1000 supports Arm CoreSight, so add it to MACHINE_FEATURES. Note that currently the FVP model doesn't support this[1] so we only enable it for MPS3. This is useful because oe-core's perf recipe will now enable coresight support automatically if this feature is present[1]. [1] https://developer.arm.com/documentation/100966/1128/Arm--Corstone-1000-FVP/Corstone-1000-FVP-modeled-components [2] oe-core c455bd03910 ("perf: enable coresight if enabled in MACHINE_FEATURES") Signed-off-by: Ross Burton <ross.burton@arm.com> --- meta-arm-bsp/conf/machine/corstone1000-mps3.conf | 3 +++ 1 file changed, 3 insertions(+)