1. 26 Aug, 2021 1 commit
  2. 19 Aug, 2021 2 commits
  3. 16 Aug, 2021 2 commits
  4. 11 Aug, 2021 1 commit
  5. 10 Aug, 2021 2 commits
  6. 05 Aug, 2021 1 commit
  7. 03 Aug, 2021 2 commits
  8. 02 Aug, 2021 2 commits
  9. 27 Jul, 2021 1 commit
  10. 24 Jul, 2021 1 commit
  11. 22 Jul, 2021 2 commits
    • Abdellatif El Khlifi's avatar
      feat: adding the diphda platform · bf3ce993
      Abdellatif El Khlifi authored
      
      
      This commit enables trusted-firmware-a with Trusted Board Boot support
      for the Diphda 64-bit platform.
      
      Diphda uses a FIP image located in the flash. The FIP contains the
      following components:
      
      - BL2
      - BL31
      - BL32
      - BL32 SPMC manifest
      - BL33
      - The TBB certificates
      
      The board boot relies on CoT (chain of trust). The trusted-firmware-a
      BL2 is extracted from the FIP and verified by the Secure Enclave
      processor. BL2 verification relies on the signature area at the
      beginning of the BL2 image. This area is needed by the SecureEnclave
      bootloader.
      
      Then, the application processor is released from reset and starts by
      executing BL2.
      
      BL2 performs the actions described in the trusted-firmware-a TBB design
      document.
      Signed-off-by: default avatarRui Miguel Silva <rui.silva@arm.com>
      Signed-off-by: default avatarAbdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
      Change-Id: Iddb1cb9c2a0324a9635e23821c210ac81dfc305d
      bf3ce993
    • Maksims Svecovs's avatar
      feat(ff-a): change manifest messaging method · bb320dbc
      Maksims Svecovs authored
      
      
      Align documentation with changes of messaging method for partition
      manifest:
            - Bit[0]: support for receiving direct message requests
            - Bit[1]: support for sending direct messages
            - Bit[2]: support for indirect messaging
            - Bit[3]: support for managed exit
      Change the optee_sp_manifest to align with the new messaging method
      description.
      Signed-off-by: default avatarMaksims Svecovs <maksims.svecovs@arm.com>
      Change-Id: I333e82c546c03698c95f0c77293018f8dca5ba9c
      bb320dbc
  12. 21 Jul, 2021 1 commit
  13. 19 Jul, 2021 1 commit
  14. 17 Jul, 2021 1 commit
  15. 16 Jul, 2021 1 commit
  16. 12 Jul, 2021 2 commits
  17. 10 Jul, 2021 2 commits
    • Pali Rohár's avatar
      fix(plat/marvell/a3k): Fix check for external dependences · 2baf5038
      Pali Rohár authored
      
      
      Old Marvell a3700_utils and mv-ddr tarballs do not have to work with
      latest TF-A code base. Marvell do not provide these old tarballs on
      Extranet anymore. Public version on github repository contains all
      patches and is working fine, so for public TF-A builds use only public
      external dependencies from git.
      Signed-off-by: default avatarPali Rohár <pali@kernel.org>
      Change-Id: Iee5ac6daa9a1826a5b80a8d54968bdbb8fe72f61
      2baf5038
    • Pali Rohár's avatar
      fix(plat/marvell/a8k): Require that MV_DDR_PATH is correctly set · 528dafc3
      Pali Rohár authored
      
      
      Target mrvl_flash depends on external mv_ddr source code which is not
      part of TF-A project. Do not expect that it is pre-downloaded at some
      specific location and require user to specify correct path to mv_ddr
      source code via MV_DDR_PATH build option.
      
      TF-A code for Armada 37x0 platform also depends on mv_ddr source code
      and already requires passing correct MV_DDR_PATH build option.
      
      So for A8K implement same checks for validity of MV_DDR_PATH option as
      are already used by TF-A code for Armada 37x0 platform.
      Signed-off-by: default avatarPali Rohár <pali@kernel.org>
      Change-Id: I792f2bfeab0cec89b1b64e88d7b2c456e22de43a
      528dafc3
  18. 30 Jun, 2021 1 commit
  19. 29 Jun, 2021 2 commits
  20. 28 Jun, 2021 1 commit
    • Max Shvetsov's avatar
      feat(sve): enable SVE for the secure world · 0c5e7d1c
      Max Shvetsov authored
      
      
      Enables SVE support for the secure world via ENABLE_SVE_FOR_SWD.
      ENABLE_SVE_FOR_SWD defaults to 0 and has to be explicitly set by the
      platform. SVE is configured during initial setup and then uses EL3
      context save/restore routine to switch between SVE configurations for
      different contexts.
      Reset value of CPTR_EL3 changed to be most restrictive by default.
      Signed-off-by: default avatarMax Shvetsov <maksims.svecovs@arm.com>
      Change-Id: I889fbbc2e435435d66779b73a2d90d1188bf4116
      0c5e7d1c
  21. 23 Jun, 2021 2 commits
  22. 14 Jun, 2021 1 commit
  23. 08 Jun, 2021 1 commit
    • Jacky Bai's avatar
      docs(imx8m): update build support for imx8mq · e3c07d2f
      Jacky Bai authored
      
      
      Due to the small OCRAM space used for TF-A, we will
      meet imx8mq build failure caused by too small RAM size.
      We CANNOT support it in TF-A CI. It does NOT mean that
      imx8mq will be dropped by NXP. NXP will still actively
      maintain it in NXP official release.
      Signed-off-by: default avatarJacky Bai <ping.bai@nxp.com>
      Change-Id: Iad726ffbc4eedc5f6770612bb9750986b9324ae9
      e3c07d2f
  24. 01 Jun, 2021 1 commit
  25. 25 May, 2021 3 commits
  26. 17 May, 2021 1 commit
  27. 13 May, 2021 1 commit
  28. 12 May, 2021 1 commit