1. 19 Jun, 2020 14 commits
  2. 18 Jun, 2020 1 commit
    • Marcin Wojtas's avatar
      plat: marvell: armada: modify PLAT_FAMILY name for 37xx SoCs · b5c850d4
      Marcin Wojtas authored
      
      
      The Marvell Armada 37xx SoCs-based platforms contain a bit
      awkward directory structure because the currently only one
      supported PLAT and PLAT_FAMILY are the same. Modify the latter
      to 'a3k' in order to improve it and keep plat/marvell/armada
      tree more consistent:
      
      plat/marvell/
      ├── armada
      │   ├── a3k
      │   │   ├── a3700
      
      [...]
      
      │   ├── a8k
      │   │   ├── a70x0
      
      [...]
      
      Change-Id: I693a6ef88e6ce49a326a3328875c90bbc186066a
      Signed-off-by: default avatarMarcin Wojtas <mw@semihalf.com>
      b5c850d4
  3. 17 Jun, 2020 3 commits
    • Manish Pandey's avatar
      Merge changes I80316689,I23cac4fb,If911e7de,I169ff358,I4e040cd5, ... into integration · 9935047b
      Manish Pandey authored
      * changes:
        ddr: a80x0: add DDR 32-bit ECC mode support
        ble: ap807: improve PLL configuration sequence
        ble: ap807: clean-up PLL configuration sequence
        ddr: a80x0: add DDR 32-bit mode support
        plat: marvell: mci: perform mci link tuning for all mci interfaces
        plat: marvell: mci: use more meaningful name for mci link tuning
        plat: marvell: a8k: remove wrong or unnecessary comments
        plat: marvell: ap807: enable snoop filter for ap807
        plat: marvell: ap807: update configuration space of each CP
        plat: marvell: ap807: use correct address for MCIx4 register
        plat: marvell: add support for PLL 2.2GHz mode
        plat: marvell: armada: make a8k_common.mk and mss_common.mk more generic
        marvell: armada: add extra level in marvell platform hierarchy
      9935047b
    • Sandrine Bailleux's avatar
    • Manish V Badarkhe's avatar
      plat/arm: Fix load address of TB_FW_CONFIG · 15865870
      Manish V Badarkhe authored
      
      
      Load address of tb_fw_config is incorrectly mentioned
      in below device trees:
      1. rdn1edge_fw_config.dts
      2. tc0_fw_config.dts
      
      Till now, tb_fw_config load-address is not being retrieved from
      device tree and hence never exeprienced any issue for tc0 and
      rdn1edge platform.
      
      For tc0 and rdn1edge platform, Load-address of tb_fw_config should
      be the SRAM base address + 0x300 (size of fw_config device tree)
      Hence updated these platform's fw_config.dts accordingly to reflect
      this load address change.
      
      Change-Id: I2ef8b05d49be10767db31384329f516df11ca817
      Signed-off-by: default avatarManish V Badarkhe <Manish.Badarkhe@arm.com>
      15865870
  4. 16 Jun, 2020 2 commits
  5. 15 Jun, 2020 3 commits
  6. 12 Jun, 2020 4 commits
  7. 11 Jun, 2020 2 commits
  8. 09 Jun, 2020 11 commits