| b3f03b20 | 21-Mar-2022 |
anans <anans@google.com> |
fix(ufs): disables controller if enabled
ufs controller needs to be disabled if already enabled, without this we noticed a crash at linkstartup during reinit
Signed-off-by: anans <anans@google.com>
fix(ufs): disables controller if enabled
ufs controller needs to be disabled if already enabled, without this we noticed a crash at linkstartup during reinit
Signed-off-by: anans <anans@google.com> Change-Id: I523c5d57c1d34f6404a6368ee3f364fbffd2e542
show more ...
|
| b08a199b | 26-Apr-2022 |
Madhukar Pappireddy <madhukar.pappireddy@arm.com> |
Merge "fix(xilinx): fix mismatching function prototype" into integration |
| 394f2ea0 | 25-Apr-2022 |
Lauren Wehrmeister <lauren.wehrmeister@arm.com> |
Merge changes Iccfa7ec6,Ide9a7af4 into integration
* changes: feat(intel): add macro to switch between different UART PORT feat(intel): add SMC support for ROM Patch SHA384 mailbox |
| cb1247e4 | 25-Apr-2022 |
Lauren Wehrmeister <lauren.wehrmeister@arm.com> |
Merge "fix(bakery_lock): add __unused for clang" into integration |
| 91665f49 | 25-Apr-2022 |
Madhukar Pappireddy <madhukar.pappireddy@arm.com> |
Merge "fix(ufs): fix cache maintenance issues" into integration |
| 5b44657a | 25-Apr-2022 |
Madhukar Pappireddy <madhukar.pappireddy@arm.com> |
Merge changes from topic "st_fwu_bkp_reg" into integration
* changes: feat(stm32mp1): retry 3 times FWU trial boot refactor(stm32mp1): update backup reg for FWU |
| 5cae3373 | 22-Apr-2022 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
docs(prerequisites): upgrade to mbed TLS 2.28.0
Upgrade to the latest and greatest 2.x release of Mbed TLS library (i.e. v2.28.0) to take advantage of their bug fixes.
Note that the Mbed TLS projec
docs(prerequisites): upgrade to mbed TLS 2.28.0
Upgrade to the latest and greatest 2.x release of Mbed TLS library (i.e. v2.28.0) to take advantage of their bug fixes.
Note that the Mbed TLS project published version 3.x some time ago. However, as this is a major release with API breakages, upgrading to 3.x might require some more involved changes in TF-A, which we are not ready to do. We shall upgrade to mbed TLS 3.x after the v2.7 release of TF-A.
Change-Id: I887dfd87893169c7be53b986e6c43338d15949d7 Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
show more ...
|
| a93084be | 21-Apr-2022 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
build(deps): upgrade to mbed TLS 2.28.0
Upgrade to the latest and greatest 2.x release of Mbed TLS library (i.e. v2.28.0) to take advantage of their bug fixes.
Note that the Mbed TLS project publis
build(deps): upgrade to mbed TLS 2.28.0
Upgrade to the latest and greatest 2.x release of Mbed TLS library (i.e. v2.28.0) to take advantage of their bug fixes.
Note that the Mbed TLS project published version 3.x some time ago. However, as this is a major release with API breakages, upgrading to 3.x might require some more involved changes in TF-A, which we are not ready to do. We shall upgrade to mbed TLS 3.x after the v2.7 release of TF-A.
Actually, the upgrade this time simply boils down to including the new source code module 'constant_time.c' into the firmware.
To quote mbed TLS v2.28.0 release notes [1]:
The mbedcrypto library includes a new source code module constant_time.c, containing various functions meant to resist timing side channel attacks. This module does not have a separate configuration option, and functions from this module will be included in the build as required.
As a matter of fact, if one is attempting to link TF-A against mbed TLS v2.28.0 without the present patch, one gets some linker errors due to missing symbols from this new module.
Apart from this, none of the items listed in mbed TLS release notes [1] directly affect TF-A. Special note on the following one:
Fix a bug in mbedtls_gcm_starts() when the bit length of the iv exceeds 2^32.
In TF-A, we do use mbedtls_gcm_starts() when the firmware decryption feature is enabled with AES-GCM as the authenticated decryption algorithm (DECRYPTION_SUPPORT=aes_gcm). However, the iv_len variable which gets passed to mbedtls_gcm_starts() is an unsigned int, i.e. a 32-bit value which by definition is always less than 2**32. Therefore, we are immune to this bug.
With this upgrade, the size of BL1 and BL2 binaries does not appear to change on a standard sample test build (with trusted boot and measured boot enabled).
[1] https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.0
Change-Id: Icd5dbf527395e9e22c8fd6b77427188bd7237fd6 Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
show more ...
|
| bc7b7098 | 25-Apr-2022 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
Merge "docs(prerequisites): update Arm compilers download link" into integration |
| 71a5543b | 15-Apr-2022 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
docs(prerequisites): update Arm compilers download link
Right now, TF-A documentation recommends downloading Arm compilers from:
https://developer.arm.com/open-source/gnu-toolchain/gnu-a/download
docs(prerequisites): update Arm compilers download link
Right now, TF-A documentation recommends downloading Arm compilers from:
https://developer.arm.com/open-source/gnu-toolchain/gnu-a/downloads
However, this page is now deprecated, as indicated by the banner at the top of the page. When navigating to the new recommended page, one can see the following note, which provides the rationale for the deprecation:
GNU Toolchain releases from Arm were published previously as two separate releases - one for A-profile and the other for R & M profiles (GNU Toolchain for A-profile processors and GNU Arm Embedded Toolchain).
Arm GNU Toolchain releases unifies these two into a single release and the previous way of releases therefore have been discontinued. However, the previous releases will continue to be available for reference.
This patch updates the link to the new recommended place for compiler downloads.
Change-Id: Iefdea3866a1af806a5db2d2288edbb63c543b8ee Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
show more ...
|
| 94909893 | 25-Apr-2022 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
Merge "docs: fix mailing lists URLs" into integration |
| 50593e69 | 21-Mar-2022 |
anans <anans@google.com> |
refactor(ufs): adds a function for fdeviceinit
time taken for device init varies based on different devices, instead of waiting for 200ms - we can poll on fdevice init until it gets cleared, similar
refactor(ufs): adds a function for fdeviceinit
time taken for device init varies based on different devices, instead of waiting for 200ms - we can poll on fdevice init until it gets cleared, similar to what linux does
Change-Id: I571649231732fde0cd6d5be89b6f14fe905fcaff Signed-off-by: anans <anans@google.com>
show more ...
|
| 5ca81820 | 19-Mar-2022 |
Sieu Mun Tang <sieu.mun.tang@intel.com> |
docs(intel): add Sieu Mun and Benjamin Jit Loon as maintainers
Add Sieu Mun Tang and Benjamin Jit Loon Lim as new Intel SocFPGA platform maintainers and remove the rest of the Intel SocFPGA platform
docs(intel): add Sieu Mun and Benjamin Jit Loon as maintainers
Add Sieu Mun Tang and Benjamin Jit Loon Lim as new Intel SocFPGA platform maintainers and remove the rest of the Intel SocFPGA platform maintainers.
Signed-off-by: Sieu Mun Tang <sieu.mun.tang@intel.com> Change-Id: Ieb9a35e278d70a12351aaccab90ddc7be09dc861
show more ...
|
| 65b13bac | 22-Apr-2022 |
Olivier Deprez <olivier.deprez@arm.com> |
Merge changes from topic "ffa_el3_spmc" into integration
* changes: feat(spmc): add support for direct req/resp feat(spmc): add support for handling FFA_ERROR ABI feat(spmc): add support for F
Merge changes from topic "ffa_el3_spmc" into integration
* changes: feat(spmc): add support for direct req/resp feat(spmc): add support for handling FFA_ERROR ABI feat(spmc): add support for FFA_MSG_WAIT feat(spmc): add function to determine the return path from the SPMC feat(spmd): enable handling of FF-A SMCs with the SPMC at EL3 feat(spmd): update SPMC init flow to use EL3 implementation feat(spmc): add FF-A secure partition manager core feat(spmc): prevent read only xlat tables with the EL3 SPMC feat(spmc): enable building of the SPMC at EL3 refactor(spm_mm): reorganize secure partition manager code
show more ...
|
| 115748b2 | 22-Apr-2022 |
Manish Pandey <manish.pandey2@arm.com> |
Merge "fix(stm32mp1): correct dtc version check" into integration |
| 429f10e3 | 22-Apr-2022 |
Yann Gautier <yann.gautier@foss.st.com> |
fix(stm32mp1): correct dtc version check
Depending on the shell used, the grep command can fail, leading to a wrong dtc version detection. Correct that by adding quotes.
Signed-off-by: Yann Gautier
fix(stm32mp1): correct dtc version check
Depending on the shell used, the grep command can fail, leading to a wrong dtc version detection. Correct that by adding quotes.
Signed-off-by: Yann Gautier <yann.gautier@foss.st.com> Change-Id: I329ec929559c94bf1bf99b127662c9d978e067cf
show more ...
|
| 6f867496 | 21-Apr-2022 |
Olivier Deprez <olivier.deprez@arm.com> |
Merge "feat(spm): add FFA_RX_ACQUIRE forwarding in SPMD" into integration |
| f4a55e6b | 21-Apr-2022 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
docs: fix mailing lists URLs
With the transition to mailman3, the URLs of TF-A and TF-A Tests mailing lists have changed. However, we still refer to the old location, which are now dead links.
Upda
docs: fix mailing lists URLs
With the transition to mailman3, the URLs of TF-A and TF-A Tests mailing lists have changed. However, we still refer to the old location, which are now dead links.
Update all relevant links throughout the documentation.
There is one link referring to a specific thread on the TF-A mailing list in the SPM documentation, for which I had to make a guess as to what's the equivalent mailman3 URL. The old URL scheme indicates that the thread dates from February 2020 but beyond that, I could not make sense of the thread id within the old URL so I picked the most likely match amongst the 3 emails posted on the subject in this time period.
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com> Reported-by: Kuohong Wang <kuohong.wang@mediatek.com> Change-Id: I83f4843afd1dd46f885df225931d8458152dbb58
show more ...
|
| 9741327d | 29-Nov-2021 |
Marc Bonnici <marc.bonnici@arm.com> |
feat(spmc): add support for direct req/resp
Enable the SPMC to handle FFA_MSG_SEND_DIRECT_REQ and FFA_MSG_SEND_DIRECT_RESP ABIs.
Signed-off-by: Marc Bonnici <marc.bonnici@arm.com> Change-Id: Ia196c
feat(spmc): add support for direct req/resp
Enable the SPMC to handle FFA_MSG_SEND_DIRECT_REQ and FFA_MSG_SEND_DIRECT_RESP ABIs.
Signed-off-by: Marc Bonnici <marc.bonnici@arm.com> Change-Id: Ia196c7405993f600e4fdbf467397ea3fb035a62a
show more ...
|
| d663fe7a | 10-Dec-2021 |
Marc Bonnici <marc.bonnici@arm.com> |
feat(spmc): add support for handling FFA_ERROR ABI
This ABI is only valid during SP initialisation to indicate failure. If this occurs during SP initialisation signal a failure, otherwise respond wi
feat(spmc): add support for handling FFA_ERROR ABI
This ABI is only valid during SP initialisation to indicate failure. If this occurs during SP initialisation signal a failure, otherwise respond with a not supported error code.
Signed-off-by: Marc Bonnici <marc.bonnici@arm.com> Change-Id: I0182a1641c0f6850e82173af333be79b594f2318
show more ...
|
| c4db76f0 | 29-Nov-2021 |
Marc Bonnici <marc.bonnici@arm.com> |
feat(spmc): add support for FFA_MSG_WAIT
Handle an incoming call of FFA_MSG_WAIT from the secure world and update the runtime state of the calling partition accordingly.
This ABI can be called in t
feat(spmc): add support for FFA_MSG_WAIT
Handle an incoming call of FFA_MSG_WAIT from the secure world and update the runtime state of the calling partition accordingly.
This ABI can be called in the following scenarios: - Used by an SP to signal it has finished initializing. - To resume the normal world after handling a secure interrupt that interrupted the normal world. - To relinquish control back to the normal world.
Signed-off-by: Marc Bonnici <marc.bonnici@arm.com> Change-Id: I929713a2280e8ec291b5b4e8f6d4b49df337228c
show more ...
|
| 20fae0a7 | 29-Nov-2021 |
Marc Bonnici <marc.bonnici@arm.com> |
feat(spmc): add function to determine the return path from the SPMC
Use knowledge of the target partition ID and source security state to determine which route should be used to exit the SPMC.
Ther
feat(spmc): add function to determine the return path from the SPMC
Use knowledge of the target partition ID and source security state to determine which route should be used to exit the SPMC.
There are 3 exit paths: 1) Return to the normal world via the SPMD, this will take care of switching contexts if required. 2) Return to the secure world when the call originated in the normal world and therefore switch contexts. 3) Return to the secure world when the call originated in the secure world, therefore we can return directly.
Signed-off-by: Marc Bonnici <marc.bonnici@arm.com> Change-Id: I4037f3a8a8519e2c9f1876be92806d2c41d0d154
show more ...
|
| bb01a673 | 29-Nov-2021 |
Marc Bonnici <marc.bonnici@arm.com> |
feat(spmd): enable handling of FF-A SMCs with the SPMC at EL3
Any FF-A SMC that arrives from the normal world is handled by the SPMD before being forwarded to the SPMC. Similarly any SMC arriving fr
feat(spmd): enable handling of FF-A SMCs with the SPMC at EL3
Any FF-A SMC that arrives from the normal world is handled by the SPMD before being forwarded to the SPMC. Similarly any SMC arriving from the secure world will hit the SPMC first and be forwarded to the SPMD if required, otherwise the SPMC will respond directly.
This allows for the existing flow of handling FF-A ABI's when the SPMC resides at a lower EL to be preserved.
In order to facilitate this flow the spmd_smc_forward function has been split and control is either passed to the SPMC or it is forwarded as before. To allow this the flags and cookie parameters must now also be passed into this method as the SPMC must be able to provide these when calling back into the SPMD handler as appropriate.
Signed-off-by: Marc Bonnici <marc.bonnici@arm.com> Change-Id: I84fee8390023295b9689067e14cd25cba23ca39b
show more ...
|
| 6da76075 | 29-Nov-2021 |
Marc Bonnici <marc.bonnici@arm.com> |
feat(spmd): update SPMC init flow to use EL3 implementation
Allow the SPMD to initialise an SPMC implementation at EL3 directly rather than at a lower EL. This includes removing the requirement to p
feat(spmd): update SPMC init flow to use EL3 implementation
Allow the SPMD to initialise an SPMC implementation at EL3 directly rather than at a lower EL. This includes removing the requirement to parse an SPMC manifest to obtain information about the SPMC implementation, in this case since the SPMD and SPMC reside in the same EL we can hardcode the required information directly.
Signed-off-by: Marc Bonnici <marc.bonnici@arm.com> Change-Id: I66d1e1b3ec2d0abbfc28b011a32445ee890a331d
show more ...
|
| 5096aeb2 | 01-Dec-2021 |
Marc Bonnici <marc.bonnici@arm.com> |
feat(spmc): add FF-A secure partition manager core
This patch introduces the core support for enabling an SPMC in EL3 as per the FF-A spec.
The current implemented functionality is targeted to enab
feat(spmc): add FF-A secure partition manager core
This patch introduces the core support for enabling an SPMC in EL3 as per the FF-A spec.
The current implemented functionality is targeted to enable initialization of the SPMC itself and initial support for bringing up a single S-EL1 SP.
This includes initialization of the SPMC's internal state, parsing of an SP's manifest, preparing the cpu contexts and appropriate system registers for the Secure Partition.
The spmc_smc_handler is the main handler for all incoming SMCs to the SPMC, FF-A ABI handlers and functionality will be implemented in subsequent patches.
Signed-off-by: Marc Bonnici <marc.bonnici@arm.com> Change-Id: Ib33c240b91e54cbd018a69fec880d02adfbe12b9
show more ...
|