1. 10 Aug, 2020 2 commits
    • Alexei Fedorov's avatar
      TF-A AMU extension: fix detection of group 1 counters. · f3ccf036
      Alexei Fedorov authored
      
      
      This patch fixes the bug when AMUv1 group1 counters was
      always assumed being implemented without checking for its
      presence which was causing exception otherwise.
      The AMU extension code was also modified as listed below:
      - Added detection of AMUv1 for ARMv8.6
      - 'PLAT_AMU_GROUP1_NR_COUNTERS' build option is removed and
      number of group1 counters 'AMU_GROUP1_NR_COUNTERS' is now
      calculated based on 'AMU_GROUP1_COUNTERS_MASK' value
      - Added bit fields definitions and access functions for
      AMCFGR_EL0/AMCFGR and AMCGCR_EL0/AMCGCR registers
      - Unification of amu.c Aarch64 and Aarch32 source files
      - Bug fixes and TF-A coding style compliant changes.
      
      Change-Id: I14e407be62c3026ebc674ec7045e240ccb71e1fb
      Signed-off-by: default avatarAlexei Fedorov <Alexei.Fedorov@arm.com>
      f3ccf036
    • Saurabh Gorecha's avatar
      sc7180 platform support · 5bd9c17d
      Saurabh Gorecha authored
      
      
      Adding support for QTI CHIP SC7180 on ATF
      
      Change-Id: I0d82d3a378036003fbd0bc4784f61464bb76ea82
      Signed-off-by: default avatarSaurabh Gorecha <sgorecha@codeaurora.org>
      Co-authored-by: default avatarMaulik Shah <mkshah@codeaurora.org>
      5bd9c17d
  2. 06 Aug, 2020 1 commit
  3. 04 Aug, 2020 1 commit
    • Grant Likely's avatar
      Use abspath to dereference $BUILD_BASE · 29214e95
      Grant Likely authored
      
      
      If the user tries to change BUILD_BASE to put the build products outside
      the build tree the compile will fail due to hard coded assumptions that
      $BUILD_BASE is a relative path. Fix by using $(abspath $(BUILD_BASE))
      to rationalize to an absolute path every time and remove the relative
      path assumptions.
      
      This patch also adds documentation that BUILD_BASE can be specified by
      the user.
      Signed-off-by: default avatarGrant Likely <grant.likely@arm.com>
      Signed-off-by: default avatarManish Pandey <manish.pandey2@arm.com>
      Change-Id: Ib1af874de658484aaffc672f30029b852d2489c8
      29214e95
  4. 03 Aug, 2020 1 commit
  5. 31 Jul, 2020 1 commit
  6. 30 Jul, 2020 5 commits
  7. 28 Jul, 2020 1 commit
    • johpow01's avatar
      Fix broken link in documentation · 526f2bdd
      johpow01 authored
      
      
      The link to the exception handling framework page on the System Design /
      Firmware Design / Section 4.3 just links to itself, so I changed it to
      link to the exception handling framework component document.
      Signed-off-by: default avatarJohn Powell <john.powell@arm.com>
      Change-Id: I6711b423a789b2b3d1921671e8497fffa8ba33d1
      526f2bdd
  8. 26 Jul, 2020 1 commit
    • Manish V Badarkhe's avatar
      SMCCC: Introduce function to check SMCCC function availability · 6f0a2f04
      Manish V Badarkhe authored
      
      
      Currently, 'SMCCC_ARCH_FEATURES' SMC call handler unconditionally
      returns 'SMC_OK' for 'SMCCC_ARCH_SOC_ID' function. This seems to
      be not correct for the platform which doesn't implement soc-id
      functionality i.e. functions to retrieve both soc-version and
      soc-revision.
      Hence introduced a platform function which will check whether SMCCC
      feature is available for the platform.
      
      Also, updated porting guide for the newly added platform function.
      
      Change-Id: I389f0ef6b0837bb24c712aa995b7176117bc7961
      Signed-off-by: default avatarManish V Badarkhe <Manish.Badarkhe@arm.com>
      6f0a2f04
  9. 23 Jul, 2020 1 commit
  10. 22 Jul, 2020 2 commits
  11. 21 Jul, 2020 4 commits
  12. 17 Jul, 2020 1 commit
  13. 10 Jul, 2020 3 commits
  14. 09 Jul, 2020 2 commits
  15. 04 Jul, 2020 3 commits
  16. 01 Jul, 2020 1 commit
  17. 30 Jun, 2020 1 commit
  18. 26 Jun, 2020 2 commits
  19. 25 Jun, 2020 3 commits
  20. 24 Jun, 2020 1 commit
    • Sandrine Bailleux's avatar
      Redirect security incident report to TrustedFirmware.org · 1367cc19
      Sandrine Bailleux authored
      
      
      All projects under the TrustedFirmware.org project now use the same
      security incident process, therefore update the disclosure/vulnerability
      reporting information in the TF-A documentation.
      
      ------------------------------------------------------------------------
      /!\ IMPORTANT /!\
      
      Please note that the email address to send these reports to has changed.
      Please do *not* use trusted-firmware-security@arm.com anymore.
      
      Similarly, the PGP key provided to encrypt emails to the security email
      alias has changed as well. Please do *not* use the former one provided
      in the TF-A source tree. It is recommended to remove it from your
      keyring to avoid any mistake. Please use the new key provided on
      TrustedFirmware.org from now on.
      ------------------------------------------------------------------------
      
      Change-Id: I14eb61017ab99182f1c45d1e156b96d5764934c1
      Signed-off-by: default avatarSandrine Bailleux <sandrine.bailleux@arm.com>
      1367cc19
  21. 23 Jun, 2020 1 commit
  22. 22 Jun, 2020 2 commits