1. 17 Dec, 2019 3 commits
    • Heiko Stuebner's avatar
      rockchip: make miniloader ddr_parameter handling optional · df5a9683
      Heiko Stuebner authored
      
      
      Transfering the regions of ddr memory to additionally protect is very much
      specific to some rockchip internal first stage bootloader and doesn't get
      used in either mainline uboot or even Rockchip's published vendor uboot
      sources.
      
      This results in a big error
          ERROR:   over or zero region, nr=0, max=10
      getting emitted on every boot for most users and such a message coming
      from early firmware might actually confuse developers working with the
      system.
      
      As this mechanism seems to be only be used by Rockchip's internal miniloader
      hide it behind a build conditional, so it doesn't confuse people too much.
      Signed-off-by: default avatarHeiko Stuebner <heiko.stuebner@theobroma-systems.com>
      Change-Id: I52c02decc60fd431ea78c7486cad5bac82bdbfbe
      df5a9683
    • Heiko Stuebner's avatar
      rockchip: px30: cleanup securing of ddr regions · f55ef85e
      Heiko Stuebner authored
      
      
      So far the px30-related ddr security was loading data for regions to secure
      from a pre-specified memory location and also setting region0 to secure
      the first megabyte of memory in hard-coded setting (top=0, end=0, meaning
      1MB).
      
      To make things more explicit and easier to read add a function doing
      the settings for specified memory areas, like other socs have and also
      add an assert to make sure any descriptor read from memory does not
      overlap the TZRAM security in region0 and TEE security in region1.
      Signed-off-by: default avatarHeiko Stuebner <heiko.stuebner@theobroma-systems.com>
      Change-Id: I78441875112bf66a62fde5f1789f4e52a78ef95f
      f55ef85e
    • Heiko Stuebner's avatar
      rockchip: px30: move secure init to separate file · d2483afa
      Heiko Stuebner authored
      
      
      Similar to others like rk3399 and rk3288 move the secure init to a
      separate file to unclutter the soc init a bit.
      Signed-off-by: default avatarHeiko Stuebner <heiko.stuebner@theobroma-systems.com>
      Change-Id: Iebb38e24f1c7fe5353f139c896fb8ca769bf9691
      d2483afa
  2. 25 Jul, 2019 1 commit
    • Ambroise Vincent's avatar
      rockchip: px30: Fix build error · 8a079e88
      Ambroise Vincent authored
      "result of '1 << 31' requires 33 bits to represent, but 'int' only has
      32 bits [-Werror=shift-overflow=]"
      
      This is treated as an error since commit 93c690eb
      
       ("Enable
      -Wshift-overflow=2 to check for undefined shift behavior")
      
      Only the actual errors are being tackled by this patch. It is up to the
      platform to choose whether there needs to be further modifications to
      the code.
      
      Change-Id: I70860ae5f2a34d7c684bd491b76da50aa04f778e
      Signed-off-by: default avatarAmbroise Vincent <ambroise.vincent@arm.com>
      8a079e88
  3. 09 Jul, 2019 1 commit
    • XiaoDong Huang's avatar
      rockchip: px30: support px30 · 010d6ae3
      XiaoDong Huang authored
      
      
      px30 is a Quad-core soc and Cortex-a53 inside.
      This patch supports the following functions:
      1. basic platform setup
      2. power up/off cpus
      3. suspend/resume cpus
      4. suspend/resume system
      5. reset system
      6. power off system
      
      Change-Id: I73d55aa978096c078242be921abe0ddca9e8f67e
      Signed-off-by: default avatarXiaoDong Huang <derrick.huang@rock-chips.com>
      010d6ae3