1. 12 Mar, 2020 1 commit
  2. 11 Mar, 2020 11 commits
  3. 10 Mar, 2020 1 commit
  4. 09 Mar, 2020 10 commits
  5. 06 Mar, 2020 5 commits
  6. 05 Mar, 2020 3 commits
  7. 04 Mar, 2020 1 commit
    • Manish Pandey's avatar
      SPMD: loading Secure Partition payloads · cb3b5344
      Manish Pandey authored
      
      
      This patch implements loading of Secure Partition packages using
      existing framework of loading other bl images.
      
      The current framework uses a statically defined array to store all the
      possible image types and at run time generates a link list and traverse
      through it to load different images.
      
      To load SPs, a new array of fixed size is introduced which will be
      dynamically populated based on number of SPs available in the system
      and it will be appended to the loadable images list.
      
      Change-Id: I8309f63595f2a71b28a73b922d20ccba9c4f6ae4
      Signed-off-by: default avatarManish Pandey <manish.pandey2@arm.com>
      cb3b5344
  8. 03 Mar, 2020 4 commits
  9. 02 Mar, 2020 1 commit
    • Leo Yan's avatar
      hikey960: Enable system power off callback · cfde1870
      Leo Yan authored
      
      
      On Hikey960 if outputs GPIO176 low level, it can tell PMIC to power off
      the whole board.  To avoid resetting the board and stay off, it also
      requires the SW2201's three switches 1/2/3 need to be all set to 0.
      
      Since current code doesn't contain complete GPIO modules and misses to
      support GPIO176.  This patch adds all known GPIO modules and initialize
      GPIO in BL31, and adds system power off callback to use GPIO176 for PMIC
      power off operation.
      
      Change-Id: Ia88859b8b7c87c061420ef75f0de3e2768667bb0
      Signed-off-by: default avatarLeo Yan <leo.yan@linaro.org>
      cfde1870
  10. 27 Feb, 2020 2 commits
  11. 26 Feb, 2020 1 commit
    • Masahiro Yamada's avatar
      uniphier: prepare uniphier_soc_info() for next SoC · dd53cfe1
      Masahiro Yamada authored
      
      
      The revision register address will be changed in the next SoC.
      
      The LSI revision is needed in order to know where the revision
      register is located, but you need to read out the revision
      register for that. This is impossible.
      
      We need to know the revision register address by other means.
      Use BL_CODE_BASE, where the base address of the TF image that is
      currently running. If it is bigger than 0x80000000 (i.e. the DRAM
      base is 0x80000000), we assume it is a legacy SoC.
      
      Change-Id: I9d7f4325fe2085a8a1ab5310025e5948da611256
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      dd53cfe1