| b5d0740e | 13-May-2025 |
Harrison Mutai <harrison.mutai@arm.com> |
build(handoff)!: switch to LibTL submodule
Removes in-tree Transfer List implementation and updates all references to use the external LibTL submodule. Updates include paths, Makefile macros, and pl
build(handoff)!: switch to LibTL submodule
Removes in-tree Transfer List implementation and updates all references to use the external LibTL submodule. Updates include paths, Makefile macros, and platform integration logic to link with LibTL as a static library.
If you cloned TF-A without the `--recurse-submodules` flag, you can ensure that this submodule is present by running:
git submodule update --init --recursive
BREAKING-CHANGE: LibTL is now included in TF-A as a submodule. Please run `git submodule update --init --recursive` if you encounter issues after migrating to the latest version of TF-A.
Change-Id: I1fa31f7b730066c27985d968698e553b00b07c38 Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
show more ...
|
| ff7daec6 | 15-Apr-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(lfa): add LFA holding pen logic
Add LFA holding logic to be used by the LFA activate SMC call to manage CPU rendezvous. All CPUs are expected to invoke the LFA activate call for the rendezvous,
feat(lfa): add LFA holding pen logic
Add LFA holding logic to be used by the LFA activate SMC call to manage CPU rendezvous. All CPUs are expected to invoke the LFA activate call for the rendezvous, until then, they will remain on a holding lock. When the final CPU calls LFA activate, it will release the holding lock after completing the activation process on that CPU, allowing the activation process on secondary CPUs to proceed.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: Iff9e40dd87420245fe5844e286d0685c1f0db289
show more ...
|
| 07de22d2 | 16-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(lfa): add initial implementation for LFA_ACTIVATE
This patch introduces the overall handling of the LFA_ACTIVATE call, including input validation and invocation flow. While this covers the core
feat(lfa): add initial implementation for LFA_ACTIVATE
This patch introduces the overall handling of the LFA_ACTIVATE call, including input validation and invocation flow. While this covers the core implementation, per-component-specific handling will be developed in a separate patch. The respective component callbacks are invoked as part of this logic.
Change-Id: Ie9d4584fc0c0abc9a9faffed62165b4461efed3a Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
show more ...
|
| 67fa182f | 15-Apr-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(lfa): add initial implementation for LFA_PRIME
This patch introduces the overall handling of the LFA_PRIME call, including input validation and invocation flow. While this covers the core imple
feat(lfa): add initial implementation for LFA_PRIME
This patch introduces the overall handling of the LFA_PRIME call, including input validation and invocation flow. While this covers the core implementation, per-component-specific handling will be developed in a separate patch. The respective component callbacks are invoked as part of this logic.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: Ie13d15d0a060ae5f9704991245d2a65c7d846047
show more ...
|
| 3f7b2862 | 15-Apr-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(lfa): implement LFA_CANCEL SMC
Check the sanity of the arguments before proceeding with the cancellation request, do platform specific cancellation operation and then reset the live activation
feat(lfa): implement LFA_CANCEL SMC
Check the sanity of the arguments before proceeding with the cancellation request, do platform specific cancellation operation and then reset the live activation states.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I3f43d03f7c7b3e6eb85b58f363b64d3c2b1dc961
show more ...
|
| 06a6f296 | 15-Apr-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(lfa): implement LFA_GET_INVENTORY SMC
This implementation primarily retrieves activation-related flags for a given fw_seq_id, including whether the firmware is activation capable, whether an up
feat(lfa): implement LFA_GET_INVENTORY SMC
This implementation primarily retrieves activation-related flags for a given fw_seq_id, including whether the firmware is activation capable, whether an update is pending activation, whether it resets the CPU during activation, whether CPU rendezvous is required, and the firmware's UUID. To support this, a platform API is called to determine whether an update is available for the specified fw_seq_id, indicating its pending activation status.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I6e702a8b313386f5668027386845ff2dae9328e7
show more ...
|
| b9dee50c | 30-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(lfa): implement LFA_GET_INFO SMC and integrate LFA build
Implement the LFA_GET_INFO SMC handler, which retrieves the number of supported firmware components and performs initial setup via the p
feat(lfa): implement LFA_GET_INFO SMC and integrate LFA build
Implement the LFA_GET_INFO SMC handler, which retrieves the number of supported firmware components and performs initial setup via the platform APIs. This forms the entry point for LFA usage and makes component metadata available for later use.
Update the build system to include LFA sources.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I4016615a88706972eff6ea5777dda6d5a3a04074
show more ...
|
| d837ccd8 | 30-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(rmm): add placeholder activator callbacks for LFA
Introduce the RMM component's activator structure for use in LFA. The 'prime' and 'activate' callbacks currently return LFA_WRONG_STATE as plac
feat(rmm): add placeholder activator callbacks for LFA
Introduce the RMM component's activator structure for use in LFA. The 'prime' and 'activate' callbacks currently return LFA_WRONG_STATE as placeholders.
These functions will be implemented in subsequent patches in this series to support actual RMM component activation logic.
Change-Id: I899ff51e4065887b7b4bbfbaa827322c51cd215c Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
show more ...
|
| f647f561 | 30-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(bl31): add placeholder activator implementation for LFA
Introduce the BL31 component's activator structure with stub implementations for the 'prime' and 'activate' callbacks.
Both callbacks cu
feat(bl31): add placeholder activator implementation for LFA
Introduce the BL31 component's activator structure with stub implementations for the 'prime' and 'activate' callbacks.
Both callbacks currently return LFA_WRONG_STATE, indicating that activation is not supported or allowed from BL31 in this context.
This activator is registered via get_bl31_activator(), allowing the platform layer to wire it into the LFA framework.
Change-Id: I4279996b218d558a45cd99d5840f0e9f8ee97f90 Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
show more ...
|
| cf48f49f | 15-Apr-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
feat(lfa): create LFA SMC handler template
As per the specification v1.0[1], added all Live Firmware Activation (LFA) SMCs, including their Function IDs (FIDs) and associated error codes. A dummy ha
feat(lfa): create LFA SMC handler template
As per the specification v1.0[1], added all Live Firmware Activation (LFA) SMCs, including their Function IDs (FIDs) and associated error codes. A dummy handler function has been created as a template. Subsequent patches will implement the handling of these SMCs.
[1]: https://developer.arm.com/documentation/den0147/latest/
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I5d6500dcff35aa4a438cd5f97f349cd57406ddce
show more ...
|
| 14acc06e | 13-Jun-2025 |
Mark Dykes <mark.dykes@arm.com> |
Merge "fix(sdei): resolve coverity error for SDEI GIC" into integration |
| 9dde2cc1 | 28-Apr-2025 |
Mark Dykes <mark.dykes@arm.com> |
fix(sdei): resolve coverity error for SDEI GIC
Fix the following issues from Coverity check:
*** CID 463142: Memory - illegal accesses (INTEGER_OVERFLOW) /services/std_svc/sdei/sdei_event.c: 79 i
fix(sdei): resolve coverity error for SDEI GIC
Fix the following issues from Coverity check:
*** CID 463142: Memory - illegal accesses (INTEGER_OVERFLOW) /services/std_svc/sdei/sdei_event.c: 79 in get_event_entry_target_pe()
*** CID 463141: Memory - illegal accesses (NEGATIVE_RETURNS) /services/std_svc/sdei/sdei_intr_mgmt.c: 64 in sdei_is_target_pe_masked()
Change-Id: I0f2928a6405f091b1ea988a43428d7032ee4c136 Signed-off-by: Mark Dykes <mark.dykes@arm.com>
show more ...
|
| f3fec61f | 28-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
fix(drtm): measure and record the DLME EP offset instead of absolute address
Update the DLME measurement logic to record only the DLME image entry point offset (`dlme_img_ep_off`) rather than the fu
fix(drtm): measure and record the DLME EP offset instead of absolute address
Update the DLME measurement logic to record only the DLME image entry point offset (`dlme_img_ep_off`) rather than the fully resolved physical address. This aligns with the DRTM specification v1.1.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I3093282a1cb0fef0aafa48aeec34770f574fa34a
show more ...
|
| 65f6936e | 27-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
fix(drtm): correct PROTECT_MEM_REGION value as per DRTM specification
The value of `PROTECT_MEM_REGION` was incorrectly set to 2. This patch updates it to 1, which aligns with the DRTM specification
fix(drtm): correct PROTECT_MEM_REGION value as per DRTM specification
The value of `PROTECT_MEM_REGION` was incorrectly set to 2. This patch updates it to 1, which aligns with the DRTM specification v1.1 for DMA protection modes.
Note: Although the DRTM implementation does not currently handle `PROTECT_MEM_REGION`, this fix ensures future compatibility and avoids misleading definitions.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I6811be8241aa4c0801352e2b9bd4872dc475ca78
show more ...
|
| 94aa3d27 | 27-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
fix(drtm): add event name data for separator event entries
Update the DRTM measurement logging to include `drtm_event_arm_sep_data` as the event name for separator events recorded in PCR-17 and PCR-
fix(drtm): add event name data for separator event entries
Update the DRTM measurement logging to include `drtm_event_arm_sep_data` as the event name for separator events recorded in PCR-17 and PCR-18.
Previously, the event name parameter was set to `NULL`, resulting in incomplete event records. This fix ensures that separator events are correctly labeled in the event log with meaningful context and it aligns with DRTM specification v1.1.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I2803d0f2e113352116d7894c2a89dfc48ed0fd85
show more ...
|
| f963578b | 05-Feb-2025 |
Boyan Karatotev <boyan.karatotev@arm.com> |
feat(lib): add a generic EXTRACT macro
The EXTRACT macro is useful to extract a named field from a numeric value, usually a register. It is functionally identical to the `ubfx` instruction and uses
feat(lib): add a generic EXTRACT macro
The EXTRACT macro is useful to extract a named field from a numeric value, usually a register. It is functionally identical to the `ubfx` instruction and uses the same #defines (REG_FIELD_SHIFT and REG_FIELD_WIDTH).
This is the same macro that we use in tftf. It works well there and is quite useful for manipulating register fields concisely.
This macro replaces the EXTRACT_FIELD macro. Their function is identical, however, EXTRACT allows for easier interoperation with the `ubfx` instruction, makes code more similar to tftf, and is more concise.
Change-Id: Ic454a87af5e5fac108c7b7cb6b6804ec65a8d0e8 Signed-off-by: Boyan Karatotev <boyan.karatotev@arm.com>
show more ...
|
| a6e01071 | 24-Apr-2025 |
Govindraj Raja <govindraj.raja@arm.com> |
Merge changes from topic "ar/cve_wa_refactor" into integration
* changes: refactor(cpus): optimize CVE checking refactor(cpus): move errata check to common code refactor(cpus): drop unused arg
Merge changes from topic "ar/cve_wa_refactor" into integration
* changes: refactor(cpus): optimize CVE checking refactor(cpus): move errata check to common code refactor(cpus): drop unused argument forward_flag
show more ...
|
| 5776045b | 23-Apr-2025 |
Govindraj Raja <govindraj.raja@arm.com> |
Merge "fix(sdei): return SDEI_EINVAL if signaling state is incorrect" into integration |
| 5a1b666d | 10-Apr-2025 |
Arvind Ram Prakash <arvind.ramprakash@arm.com> |
refactor(cpus): move errata check to common code
This patch centralizes some of the Errata ABI code that could be used for checking if an Errata has been applied to cpu library since the function is
refactor(cpus): move errata check to common code
This patch centralizes some of the Errata ABI code that could be used for checking if an Errata has been applied to cpu library since the function is mostly generic.
Signed-off-by: Arvind Ram Prakash <arvind.ramprakash@arm.com> Change-Id: I2c6d4468f7125d4d99ccdebc5ea8f9e4390360cc
show more ...
|
| 50de8867 | 31-Mar-2025 |
Arvind Ram Prakash <arvind.ramprakash@arm.com> |
refactor(cpus): drop unused argument forward_flag
This patch removes the unused argument forward_flag from verify_errata_implemented function.
Signed-off-by: Arvind Ram Prakash <arvind.ramprakash@a
refactor(cpus): drop unused argument forward_flag
This patch removes the unused argument forward_flag from verify_errata_implemented function.
Signed-off-by: Arvind Ram Prakash <arvind.ramprakash@arm.com> Change-Id: Ib1fcbe081e94657e21d983e0db59ceec9993b696
show more ...
|
| b142ede7 | 07-Oct-2024 |
Igor Podgainõi <igor.podgainoi@arm.com> |
fix(sdei): return SDEI_EINVAL if signaling state is incorrect
In case a step is omitted when an SDEI event is registered, enabled, unmasked and then signaled, incorrect code paths may be reached.
T
fix(sdei): return SDEI_EINVAL if signaling state is incorrect
In case a step is omitted when an SDEI event is registered, enabled, unmasked and then signaled, incorrect code paths may be reached.
This patch adds additional checks to return early from such an incorrect state.
Change-Id: Ia2753e9a1b95544e1afa72603574fe830f51ea9f Signed-off-by: Igor Podgainõi <igor.podgainoi@arm.com> Signed-off-by: Mark Dykes <mark.dykes@arm.com>
show more ...
|
| 640175ce | 17-Apr-2025 |
Madhukar Pappireddy <madhukar.pappireddy@arm.com> |
Merge "fix(el3-spmc): fix FF-A v1.2 version check" into integration |
| 06b99f7a | 17-Apr-2025 |
Manish V Badarkhe <manish.badarkhe@arm.com> |
Merge changes from topic "hm/evlog" into integration
* changes: refactor(measured-boot): refine event log lib docs refactor(fvp): explicitly handle event log errors feat(measured-boot): make e
Merge changes from topic "hm/evlog" into integration
* changes: refactor(measured-boot): refine event log lib docs refactor(fvp): explicitly handle event log errors feat(measured-boot): make event log lib standalone
show more ...
|
| ec56d595 | 15-Apr-2025 |
Soby Mathew <soby.mathew@arm.com> |
Merge changes from topic "sm/rpkm" into integration
* changes: docs(rmmd): document the EL3-RMM IDE KM Interface feat(trp): test el3-rmm ide km interface feat(rmmd): el3-rmm ide key management
Merge changes from topic "sm/rpkm" into integration
* changes: docs(rmmd): document the EL3-RMM IDE KM Interface feat(trp): test el3-rmm ide km interface feat(rmmd): el3-rmm ide key management interface
show more ...
|
| cb03020e | 27-Feb-2025 |
Harrison Mutai <harrison.mutai@arm.com> |
feat(measured-boot): make event log lib standalone
Remove dependencies on TF-A so the library can be conveniently exported by other projets. The main changes are to remove explicit error handling, a
feat(measured-boot): make event log lib standalone
Remove dependencies on TF-A so the library can be conveniently exported by other projets. The main changes are to remove explicit error handling, and ensure that functions instead return errno codes that consumers can rely on instead. Some work has also been done to make the function naming a little more consistent.
Change-Id: Ic182dfe7dd6f56a4b73e0da4c9051813938cfe44 Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
show more ...
|