1. 29 Jan, 2021 3 commits
    • Pali Rohár's avatar
      docs: marvell: Update info about WTMI_IMG option · 711a6bb7
      Pali Rohár authored
      
      
      Default WTMI_IMG value was documented incorrectly. Also WTMI_IMG name may
      be misleading as this option does not specify full WTMI image, just a main
      loop (e.g. fuse.bin or custom RTOS image) without hardware initialization
      code (DDR, CPU and clocks).
      Signed-off-by: default avatarPali Rohár <pali@kernel.org>
      Change-Id: I3de4a27ce2165b962fa628c992fd8f80151efd7c
      711a6bb7
    • Pali Rohár's avatar
      plat: marvell: armada: a3k: Add a new target mrvl_uart which builds UART image · 8b920973
      Pali Rohár authored
      
      
      This change separates building of flash and UART images, so it is possible
      to build only one of these images. Also this change allows make to build
      them in parallel.
      
      Target mrvl_flash now builds only flash image and mrvl_uart only UART
      image. This change reflects it also in the documentation.
      Signed-off-by: default avatarPali Rohár <pali@kernel.org>
      Change-Id: Ie9ce4538d52188dd26d99dfeeb5ad171a5b818f3
      8b920973
    • Pali Rohár's avatar
      plat: marvell: armada: a3k: Allow use of the system Crypto++ library · 8708a884
      Pali Rohár authored
      
      
      This change introduces two new A3720 parameters, CRYPTOPP_LIBDIR and
      CRYPTOPP_INCDIR, which can be used to specify directory paths to
      pre-compiled Crypto++ library and header files.
      
      When both new parameters are specified then the source code of Crypto++ via
      CRYPTOPP_PATH parameter is not needed. And therefore it allows TF-A build
      process to use system Crypto++ library.
      Signed-off-by: default avatarPali Rohár <pali@kernel.org>
      Change-Id: I6d440f86153373b11b8d098bb68eb7325e86b20b
      8708a884
  2. 28 Jan, 2021 1 commit
  3. 26 Jan, 2021 1 commit
  4. 14 Jan, 2021 1 commit
  5. 05 Jan, 2021 1 commit
    • Marek Behún's avatar
      plat: marvell: armada: a3k: support doing system reset via CM3 secure coprocessor · d9243f26
      Marek Behún authored
      
      
      Introduce a new build option CM3_SYSTEM_RESET for A3700 platform, which,
      when enabled, adds code to the PSCI reset handler to try to do system
      reset by the WTMI firmware running on the Cortex-M3 secure coprocessor.
      (This function is exposed via the mailbox interface.)
      
      The reason is that the Turris MOX board has a HW bug which causes reset
      to hang unpredictably. This issue can be solved by putting the board in
      a specific state before reset.
      Signed-off-by: default avatarMarek Behún <marek.behun@nic.cz>
      Change-Id: I3f60b9f244f334adcd33d6db6a361fbc8b8d209f
      d9243f26
  6. 19 Nov, 2020 1 commit
  7. 11 Oct, 2020 1 commit
  8. 04 Oct, 2020 1 commit
  9. 30 Jul, 2020 1 commit
  10. 10 Jul, 2020 1 commit
    • Konstantin Porotchkin's avatar
      plat: marvell: armada: a8k: change CCU LLC SRAM mapping · 0a977b9b
      Konstantin Porotchkin authored
      
      
      The LLC SRAM will be enabled in OP-TEE OS for usage as secure storage.
      The CCU have to prepare SRAM window, but point to the DRAM-0 target
      until the SRAM is actually enabled.
      This patch changes CCU SRAM window target to DRAM-0
      Remove dependence between LLC_SRAM and LLC_ENABLE and update the
      build documentation.
      The SRAМ base moved to follow the OP-TEE SHMEM area (0x05400000)
      
      Change-Id: I85c2434a3d515ec37da5ae8eb729e3280f91c456
      Signed-off-by: default avatarKonstantin Porotchkin <kostap@marvell.com>
      0a977b9b
  11. 19 Jun, 2020 1 commit
  12. 06 Jun, 2020 2 commits
  13. 08 Jan, 2020 1 commit
  14. 03 Jan, 2020 1 commit
  15. 27 Nov, 2019 1 commit
    • Paul Beesley's avatar
      doc: Split the User Guide into multiple files · 43f35ef5
      Paul Beesley authored
      
      
      The User Guide document has grown organically over time and
      now covers a wide range of topics, making it difficult to
      skim read and extract information from. Currently, it covers
      these topics and maybe a couple more:
      
      - Requirements (hardware, tools, libs)
      - Checking out the repo
      - Basic build instructions
      - A comprehensive list of build flags
      - FIP packaging
      - Building specifically for Juno
      - Firmware update images
      - EL3 payloads
      - Preloaded BL33 boot flow
      - Running on FVPs
      - Running on Juno
      
      I have separated these out into a few groups that become new
      documents. Broadly speaking, build instructions for the tools,
      for TF-A generally, and for specific scenarios are separated.
      Content relating to specific platforms (Juno and the FVPs are
      Arm-specific platforms, essentially) has been moved into the
      documentation that is specific to those platforms, under
      docs/plat/arm.
      
      Change-Id: Ica87c52d8cd4f577332be0b0738998ea3ba3bbec
      Signed-off-by: default avatarPaul Beesley <paul.beesley@arm.com>
      43f35ef5
  16. 20 Sep, 2019 1 commit
    • Paul Beesley's avatar
      doc: Render Marvell platform documents · 2966defa
      Paul Beesley authored
      
      
      The documentation for Marvell platforms was not included in the
      rendered document output until now because, while it was mostly
      valid RST format, the files were saved with a .txt extension.
      
      This patch corrects some RST formatting errors, creates a document
      tree (index page) for the Marvell documents, and adds the Marvell
      subtree to the main index.
      
      Change-Id: Id7d4ac37eded636f8f62322a153e1e5f652ff51a
      Signed-off-by: default avatarPaul Beesley <paul.beesley@arm.com>
      2966defa