1. 11 Jan, 2018 1 commit
  2. 09 Jan, 2018 4 commits
  3. 04 Jan, 2018 1 commit
  4. 03 Jan, 2018 1 commit
  5. 20 Dec, 2017 2 commits
  6. 19 Dec, 2017 1 commit
  7. 18 Dec, 2017 1 commit
  8. 12 Dec, 2017 5 commits
  9. 06 Dec, 2017 3 commits
    • Antonio Nino Diaz's avatar
      fvp: Disable SYSTEM_SUSPEND when ARM_BL31_IN_DRAM · 7d44ac1e
      Antonio Nino Diaz authored
      
      
      After returning from SYSTEM_SUSPEND state, BL31 reconfigures the
      TrustZone Controller during the boot sequence. If BL31 is placed in
      TZC-secured DRAM, it will try to change the permissions of the memory it
      is being executed from, causing an exception.
      
      The solution is to disable SYSTEM_SUSPEND when the Trusted Firmware has
      been compiled with ``ARM_BL31_IN_DRAM=1``.
      
      Change-Id: I96dc50decaacd469327c6b591d07964726e58db4
      Signed-off-by: default avatarAntonio Nino Diaz <antonio.ninodiaz@arm.com>
      7d44ac1e
    • Antonio Nino Diaz's avatar
      SPM: Remove ARM platforms header from SPM common code · 2633dfeb
      Antonio Nino Diaz authored
      
      
      Common code mustn't include ARM platforms headers.
      
      Change-Id: Ib6e4f5a77c2d095e6e8c3ad89c89cb1959cd3043
      Signed-off-by: default avatarAntonio Nino Diaz <antonio.ninodiaz@arm.com>
      2633dfeb
    • Leo Yan's avatar
      Hikey960: Change to use recommended power state id format · fdae60b6
      Leo Yan authored
      
      
      ARM Power State Coordination Interface (ARM DEN 0022D) chapter
      6.5 "Recommended StateID Encoding" defines the state ID which can be
      used by platforms. The recommended power states can be presented by
      below values; and it divides into three fields, every field has 4 bits
      to present power states corresponding to core level, cluster level and
      system level.
      
        0: Run
        1: Standby
        2: Retention
        3: Powerdown
      
      This commit changes to use upper recommended power states definition on
      Hikey960; and changes the power state validate function to check the
      power state passed from kernel side.
      Signed-off-by: default avatarLeo Yan <leo.yan@linaro.org>
      fdae60b6
  10. 05 Dec, 2017 1 commit
  11. 02 Dec, 2017 1 commit
  12. 01 Dec, 2017 1 commit
  13. 30 Nov, 2017 1 commit
    • David Cunado's avatar
      Do not enable SVE on pre-v8.2 platforms · 3872fc2d
      David Cunado authored
      
      
      Pre-v8.2 platforms such as the Juno platform does not have
      the Scalable Vector Extensions implemented and so the build
      option ENABLE_SVE is set to zero.
      
      This has a minor performance improvement with no functional
      impact.
      
      Change-Id: Ib072735db7a0247406f8b60e325b7e28b1e04ad1
      Signed-off-by: default avatarDavid Cunado <david.cunado@arm.com>
      3872fc2d
  14. 29 Nov, 2017 4 commits
    • Soby Mathew's avatar
      Juno AArch32: Remove duplicate definition of bl2 platform API · a9f9b608
      Soby Mathew authored
      
      
      The bl2_early_platform_setup() and bl2_platform_setup() were
      redefined for Juno AArch32 eventhough CSS platform layer had
      same definition for them. The CSS definitions definitions were
      previously restricted to EL3_PAYLOAD_BASE builds and this is now
      modified to include the Juno AArch32 builds as well thus
      allowing us to remove the duplicate definitions in Juno platform
      layer.
      
      Change-Id: Ibd1d8c1428cc1d51ac0ba90f19f5208ff3278ab5
      Signed-off-by: default avatarSoby Mathew <soby.mathew@arm.com>
      a9f9b608
    • Soby Mathew's avatar
      ARM platforms: Fixup AArch32 builds · 5744e874
      Soby Mathew authored
      
      
      This patch fixes a couple of issues for AArch32 builds on ARM reference
      platforms :
      
      1. The arm_def.h previously defined the same BL32_BASE value for AArch64 and
         AArch32 build. Since BL31 is not present in AArch32 mode, this meant that
         the BL31 memory is empty when built for AArch32. Hence this patch allocates
         BL32 to the memory region occupied by BL31 for AArch32 builds.
      
         As a side-effect of this change, the ARM_TSP_RAM_LOCATION macro cannot
         be used to control the load address of BL32 in AArch32 mode which was
         never the intention of the macro anyway.
      
      2. A static assert is added to sp_min linker script to check that the progbits
         are within the bounds expected when overlaid with other images.
      
      3. Fix specifying `SPD` when building Juno for AArch32 mode. Due to the quirks
         involved when building Juno for AArch32 mode, the build option SPD needed to
         specifed. This patch corrects this and also updates the documentation in the
         user-guide.
      
      4. Exclude BL31 from the build and FIP when building Juno for AArch32 mode. As
         a result the previous assumption that BL31 must be always present is removed
         and the certificates for BL31 is only generated if `NEED_BL31` is defined.
      
      Change-Id: I1c39bbc0abd2be8fbe9f2dea2e9cb4e3e3e436a8
      Signed-off-by: default avatarSoby Mathew <soby.mathew@arm.com>
      5744e874
    • Antonio Nino Diaz's avatar
      Replace magic numbers in linkerscripts by PAGE_SIZE · a2aedac2
      Antonio Nino Diaz authored
      
      
      When defining different sections in linker scripts it is needed to align
      them to multiples of the page size. In most linker scripts this is done
      by aligning to the hardcoded value 4096 instead of PAGE_SIZE.
      
      This may be confusing when taking a look at all the codebase, as 4096
      is used in some parts that aren't meant to be a multiple of the page
      size.
      
      Change-Id: I36c6f461c7782437a58d13d37ec8b822a1663ec1
      Signed-off-by: default avatarAntonio Nino Diaz <antonio.ninodiaz@arm.com>
      a2aedac2
    • Dimitris Papastamos's avatar
      fvp: Enable the Activity Monitor Unit extensions by default · 3a6a9adc
      Dimitris Papastamos authored
      
      
      Change-Id: I96de88f44c36681ad8a70430af8e01016394bd14
      Signed-off-by: default avatarDimitris Papastamos <dimitris.papastamos@arm.com>
      3a6a9adc
  15. 22 Nov, 2017 2 commits
  16. 20 Nov, 2017 1 commit
    • Dimitris Papastamos's avatar
      Refactor Statistical Profiling Extensions implementation · 281a08cc
      Dimitris Papastamos authored
      
      
      Factor out SPE operations in a separate file.  Use the publish
      subscribe framework to drain the SPE buffers before entering secure
      world.  Additionally, enable SPE before entering normal world.
      
      A side effect of this change is that the profiling buffers are now
      only drained when a transition from normal world to secure world
      happens.  Previously they were drained also on return from secure
      world, which is unnecessary as SPE is not supported in S-EL1.
      
      Change-Id: I17582c689b4b525770dbb6db098b3a0b5777b70a
      Signed-off-by: default avatarDimitris Papastamos <dimitris.papastamos@arm.com>
      281a08cc
  17. 13 Nov, 2017 7 commits
  18. 09 Nov, 2017 1 commit
  19. 08 Nov, 2017 1 commit
  20. 06 Nov, 2017 1 commit
    • Masahiro Yamada's avatar
      uniphier: make sure to create build directory before ROT key · 3c946152
      Masahiro Yamada authored
      
      
      Building the UniPhier platform in parallel with TRUSTED_BOARD_BOOT=1
      could fail due to non-existing directory.  It might be difficult to
      reproduce, but here is an easier way to trigger the problem:
      
      $ make PLAT=uniphier TRUSTED_BOARD_BOOT=1 MBEDTLS_DIR=mbedtls certificates
        OPENSSL build/uniphier/release/rot_key.pem
      /bin/sh: 1: cannot create build/uniphier/release/rot_key.pem: Directory nonexistent
      make: *** [build/uniphier/release/rot_key.pem] Error 2
      
      The $(ROT_KEY) must depend on $(BUILD_PLAT) so that the build directory
      is created before the key.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      3c946152