1. 07 Dec, 2020 1 commit
  2. 30 Mar, 2020 1 commit
  3. 24 Jan, 2020 1 commit
  4. 23 Jan, 2020 1 commit
  5. 15 Jan, 2020 1 commit
  6. 07 Jan, 2020 1 commit
  7. 01 Jul, 2019 1 commit
  8. 01 Feb, 2019 1 commit
  9. 09 Jan, 2019 6 commits
  10. 04 Jan, 2019 1 commit
    • Antonio Nino Diaz's avatar
      Sanitise includes across codebase · 09d40e0e
      Antonio Nino Diaz authored
      Enforce full include path for includes. Deprecate old paths.
      
      The following folders inside include/lib have been left unchanged:
      
      - include/lib/cpus/${ARCH}
      - include/lib/el3_runtime/${ARCH}
      
      The reason for this change is that having a global namespace for
      includes isn't a good idea. It defeats one of the advantages of having
      folders and it introduces problems that are sometimes subtle (because
      you may not know the header you are actually including if there are two
      of them).
      
      For example, this patch had to be created because two headers were
      called the same way: e0ea0928 ("Fix gpio includes of mt8173 platform
      to avoid collision."). More recently, this patch has had similar
      problems: 46f9b2c3 ("drivers: add tzc380 support").
      
      This problem was introduced in commit 4ecca339
      
       ("Move include and
      source files to logical locations"). At that time, there weren't too
      many headers so it wasn't a real issue. However, time has shown that
      this creates problems.
      
      Platforms that want to preserve the way they include headers may add the
      removed paths to PLAT_INCLUDES, but this is discouraged.
      
      Change-Id: I39dc53ed98f9e297a5966e723d1936d6ccf2fc8f
      Signed-off-by: default avatarAntonio Nino Diaz <antonio.ninodiaz@arm.com>
      09d40e0e
  11. 08 Nov, 2018 1 commit
    • Antonio Nino Diaz's avatar
      Standardise header guards across codebase · c3cf06f1
      Antonio Nino Diaz authored
      
      
      All identifiers, regardless of use, that start with two underscores are
      reserved. This means they can't be used in header guards.
      
      The style that this project is now to use the full name of the file in
      capital letters followed by 'H'. For example, for a file called
      "uart_example.h", the header guard is UART_EXAMPLE_H.
      
      The exceptions are files that are imported from other projects:
      
      - CryptoCell driver
      - dt-bindings folders
      - zlib headers
      
      Change-Id: I50561bf6c88b491ec440d0c8385c74650f3c106e
      Signed-off-by: default avatarAntonio Nino Diaz <antonio.ninodiaz@arm.com>
      c3cf06f1
  12. 20 Jul, 2018 1 commit
  13. 21 Jun, 2018 1 commit
  14. 17 May, 2018 1 commit
  15. 15 Mar, 2018 1 commit
    • Jolly Shah's avatar
      zynqmp: Use DDR memory when DEBUG is enabled · 3077f8d9
      Jolly Shah authored
      
      
      Define default DDR location to which ATF has to compiled
      if DEBUG option is enabled. This is required now, as the ATF cant fit
      in OCM with DEBUG option enabled. The default value is 0x1000 and can be
      used till 0x7ffff. User can still override as per wish/requirement
      using current commandline options.
      
      Signed-off-by: default avatarJolly Shah <jollys@xilinx.com>
      3077f8d9
  16. 27 Feb, 2018 1 commit
  17. 17 Oct, 2017 1 commit
  18. 03 May, 2017 1 commit
  19. 06 Jan, 2017 1 commit
  20. 16 Nov, 2016 1 commit
  21. 13 Sep, 2016 2 commits
  22. 11 Jul, 2016 1 commit
  23. 24 May, 2016 1 commit
  24. 25 Apr, 2016 1 commit
    • Soren Brinkmann's avatar
      zynqmp: Revise memory configuration options · 01555332
      Soren Brinkmann authored
      
      
      Drop the current configuration options for selecting the location of
      the ATF and TSP (ZYNQMP_ATF_LOCATION, ZYNQMP_TSP_RAM_LOCATION).
      The new configuration provides one default setup (ATF in OCM,
      BL32 in DRAM). Additionally, the new configuration options
       - ZYNQMP_ATF_MEM_BASE
       - ZYNQMP_ATF_MEM_SIZE
       - ZYNQMP_BL32_MEM_BASE
       - ZYNQMP_BL32_MEM_SIZE
      can be used to freely configure the memory locations used for ATF and
      secure payload.
      
      Also, allow setting the BL33 entry point via PRELOADED_BL33_BASE.
      
      Cc: petalinux-dev@xilinx.com
      Signed-off-by: default avatarSoren Brinkmann <soren.brinkmann@xilinx.com>
      Acked-by: default avatarAlistair Francis <alistair.francis@xilinx.com>
      01555332
  25. 14 Apr, 2016 1 commit
    • Gerald Lejeune's avatar
      Dump platform-defined regs in crash reporting · 9ff67fa6
      Gerald Lejeune authored
      
      
      It is up to the platform to implement the new plat_crash_print_regs macro to
      report all relevant platform registers helpful for troubleshooting.
      
      plat_crash_print_regs merges or calls previously defined plat_print_gic_regs
      and plat_print_interconnect_regs macros for each existing platforms.
      
      NOTE: THIS COMMIT REQUIRES ALL PLATFORMS THAT ENABLE THE `CRASH_REPORTING`
      BUILD FLAG TO MIGRATE TO USE THE NEW `plat_crash_print_regs()` MACRO. BY
      DEFAULT, `CRASH_REPORTING` IS ENABLED IN DEBUG BUILDS FOR ALL PLATFORMS.
      
      Fixes: arm-software/tf-issues#373
      
      Signed-off-by: default avatarGerald Lejeune <gerald.lejeune@st.com>
      9ff67fa6
  26. 06 Apr, 2016 1 commit