1. 19 Jun, 2018 2 commits
    • Benjamin Fair's avatar
      ti: k3: common: Populate BL32 and BL33 entrypoint · a546d25b
      Benjamin Fair authored
      
      
      Because there is no BL2, BL31 must determine the entrypoint and memory
      location of BL32 and BL33 on its own.
      
      BL32_BASE and PRELOADED_BL33_BASE will be set in the corresponding board
      makefile. We also allow a DTB address to be specified for cases when BL33
      is a Linux image.
      
      NOTE: It is possible to pull in this information from device tree as
      well, however libfdt does not contain the required hooks to make this
      happen at this point in time.
      Signed-off-by: default avatarBenjamin Fair <b-fair@ti.com>
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      a546d25b
    • Nishanth Menon's avatar
      ti: k3: Setup initial files for platform · 1841c533
      Nishanth Menon authored
      
      
      Create the baseline Makefile, platform definitions file and platform
      specific assembly macros file. This includes first set of constants
      for the platform including cache sizes and linker format and a stub for
      BL31 and the basic memory layout
      
      K3 SoC family of processors do not use require a BL1 or BL2 binary,
      since such functions are provided by an system controller on the SoC.
      This lowers the burden of ATF to purely managing the local ARM cores
      themselves.
      Signed-off-by: default avatarBenjamin Fair <b-fair@ti.com>
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      1841c533