1. 27 Oct, 2016 1 commit
  2. 26 Oct, 2016 2 commits
  3. 24 Oct, 2016 5 commits
  4. 21 Oct, 2016 1 commit
  5. 18 Oct, 2016 2 commits
  6. 17 Oct, 2016 4 commits
  7. 14 Oct, 2016 2 commits
  8. 13 Oct, 2016 6 commits
  9. 12 Oct, 2016 11 commits
    • danh-arm's avatar
      Merge pull request #732 from dp-arm/dp/pmf-doc · b314c9fa
      danh-arm authored
      PMF: Add documentation
      b314c9fa
    • dp-arm's avatar
      PMF: Add documentation · 514a94c2
      dp-arm authored
      
      
      Add a Performance Measurement Framework (PMF) section
      to the firmware design document.
      
      Change-Id: I5953bd3b1067501f190164c8827d2b0d8022fc0b
      Signed-off-by: default avatardp-arm <dimitris.papastamos@arm.com>
      514a94c2
    • dp-arm's avatar
      Remove non-standard <sys/cdefs.h> include from uuid.h · 9e23f9ab
      dp-arm authored
      This include provides nothing useful for TF and prevents building
      the fiptool using musl libc[0].
      
      [0] https://www.musl-libc.org/
      
      
      
      Change-Id: Ied35e16b9ea2b40213433f2a8185dddc59077884
      Signed-off-by: default avatardp-arm <dimitris.papastamos@arm.com>
      9e23f9ab
    • dp-arm's avatar
      Add PMF instrumentation points in TF · 872be88a
      dp-arm authored
      
      
      In order to quantify the overall time spent in the PSCI software
      implementation, an initial collection of PMF instrumentation points
      has been added.
      
      Instrumentation has been added to the following code paths:
      
      - Entry to PSCI SMC handler.  The timestamp is captured as early
        as possible during the runtime exception and stored in memory
        before entering the PSCI SMC handler.
      
      - Exit from PSCI SMC handler.  The timestamp is captured after
        normal return from the PSCI SMC handler or if a low power state
        was requested it is captured in the bl31 warm boot path before
        return to normal world.
      
      - Entry to low power state.  The timestamp is captured before entry
        to a low power state which implies either standby or power down.
        As these power states are mutually exclusive, only one timestamp
        is defined to describe both.  It is possible to differentiate between
        the two power states using the PSCI STAT interface.
      
      - Exit from low power state.  The timestamp is captured after a standby
        or power up operation has completed.
      
      To calculate the number of cycles spent running code in Trusted Firmware
      one can perform the following calculation:
      
      (exit_psci - enter_psci) - (exit_low_pwr - enter_low_pwr).
      
      The resulting number of cycles can be converted to time given the
      frequency of the counter.
      
      Change-Id: Ie3b8f3d16409b6703747093b3a2d5c7429ad0166
      Signed-off-by: default avatardp-arm <dimitris.papastamos@arm.com>
      872be88a
    • dp-arm's avatar
      Introduce ARM SiP service · f10796a0
      dp-arm authored
      
      
      This patch adds ARM SiP service for use by ARM standard platforms.
      This service is added to support the SMC interface for the Performance
      measurement framework(PMF).
      
      Change-Id: I26f5712f9ab54f5f721dd4781e35a16f40aacc44
      Signed-off-by: default avatardp-arm <dimitris.papastamos@arm.com>
      f10796a0
    • danh-arm's avatar
      Merge pull request #731 from danh-arm/an/fix-juno-doc · 2c8df7c1
      danh-arm authored
      Fix documentation of bootwrapper boot on juno
      2c8df7c1
    • Antonio Nino Diaz's avatar
      Fix documentation of bootwrapper boot on juno · 7486eb04
      Antonio Nino Diaz authored
      
      
      The user guide incorrectly claimed that it is possible to load a
      bootwrapped kernel over JTAG on Juno in the same manner as an EL3
      payload. In the EL3 payload boot flow, some of the platform
      initialisations in BL2 are modified. In particular, the TZC settings
      are modified to allow unrestricted access to DRAM. This in turn allows
      the debugger to access the DRAM and therefore to load the image there.
      
      In the BL33-preloaded boot flow though, BL2 uses the default TZC
      programming, which prevent access to most of the DRAM from secure state.
      When execution reaches the SPIN_ON_BL1_EXIT loop, the MMU is disabled
      and thus DS-5 presumably issues secure access transactions while trying
      to load the image, which fails.
      
      One way around it is to stop execution at the end of BL2 instead. At
      this point, the MMU is still enabled and the DRAM is mapped as
      non-secure memory. Therefore, the debugger is allowed to access this
      memory in this context and to sucessfully load the bootwrapped kernel in
      DRAM. The user guide is updated to suggest this alternative method.
      Co-Authored-By: default avatarSandrine Bailleux <sandrine.bailleux@arm.com>
      Signed-off-by: default avatarDan Handley <dan.handley@arm.com>
      
      Change-Id: I537ea1c6d2f96edc06bc3f512e770c748bcabe94
      7486eb04
    • danh-arm's avatar
      Merge pull request #728 from yatharth-arm/yk/AArch32_porting_doc · c81894d7
      danh-arm authored
      AArch32: Update firmware-design.md
      c81894d7
    • danh-arm's avatar
      Merge pull request #727 from soby-mathew/sm/PSCI_lib_doc · ea68f8c7
      danh-arm authored
      AArch32: Update user-guide and add DTBs
      ea68f8c7
    • danh-arm's avatar
      Merge pull request #726 from soby-mathew/sm/fix_dt · 2010cf73
      danh-arm authored
      Fix GICv3 DT to include psci system off/reset
      2010cf73
    • danh-arm's avatar
      Merge pull request #725 from jeenu-arm/fix-duplicate-title · c31e707e
      danh-arm authored
      Docs: Rename duplicate title in porting guide
      c31e707e
  10. 11 Oct, 2016 4 commits
    • Soby Mathew's avatar
      AArch32: Update user-guide and add DTBs · 5e21d795
      Soby Mathew authored
      This patch adds necessary updates for building and running Trusted
      Firmware for AArch32 to user-guide.md. The instructions for running
      on both `FVP_Base_AEMv8A-AEMv8A` in AArch32 mode and
      `FVP_Base_Cortex-A32x4` models are added. The device tree files for
      AArch32 Linux kernel are also added in the `fdts` folder.
      
      Change-Id: I0023b6b03e05f32637cb5765fdeda8c8df2d0d3e
      5e21d795
    • Yatharth Kochar's avatar
      AArch32: Update firmware-design.md · 9a3236ea
      Yatharth Kochar authored
      This patch updates the firmware-design.md for AArch32 related changes.
      
      Change-Id: Idf392a44861ab9c1f59f3de4f3435f508b17c678
      9a3236ea
    • Jeenu Viswambharan's avatar
      Docs: Rename duplicate title in porting guide · ec2653a7
      Jeenu Viswambharan authored
      Fix one of the two titles that ended up being the same, although both
      describe different things.
      
      Change-Id: I66ecf369643709898ee4c014659d8f85c0480643
      ec2653a7
    • Soby Mathew's avatar
      Fix GICv3 DT to include psci system off/reset · 78c4f192
      Soby Mathew authored
      The `fvp-base-gicv3-psci` and `fvp-foundation-gicv3-psci` device tree source
      files did not have psci node entries for `system off` and `system reset`.
      Also the DTS files included `rtsm_ve-motherboard-no_psci.dtsi` instead of
      `rtsm_ve-motherboard.dtsi`. As a result, the Linux kernel failed to invoke
      the PSCI_SYSTEM_OFF/RESET API when being shutdown/reset. This patch corrects
      this problem and also updates the corresponding DTB files.
      
      This patch also removes `rtsm_ve-motherboard-no_psci.dtsi` and
      `fvp-foundation-motherboard-no_psci.dtsi` files as they are no longer used.
      
      Change-Id: I8ba61a1323035f7508cae663bb490ac0e8a64618
      78c4f192
  11. 10 Oct, 2016 1 commit
  12. 29 Sep, 2016 1 commit