public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/3] arm64: zynqmp: Add support for running U-Boot in EL3 again
Date: Mon, 23 Mar 2020 14:57:57 +0100	[thread overview]
Message-ID: <cover.1584971878.git.michal.simek@xilinx.com> (raw)

Hi,

in past without PMU fw it was possible to run U-Boot in EL3. Firmware
changes made ATF required that's why generation was done like this.
But some recent changes (especially passing PMUFW object to PMU from SPL)
introduce the whole infrastructure for talking to PMU via IPI interface.
That's why this interface can be reused and run U-Boot in EL3 again.

Based on it I have fixed mkimage_fit_atf.sh script to generate
u-boot.its/itb based on ATF availability but still producing working image
without it.

Also found two issues which should be fixed to get U-Boot work in EL3.

Thanks,
Michal


Michal Simek (3):
  firmware: zynqmp: Enable IPI code calling also in EL3
  arm64: zynqmp: Reorder parameters for zynqmp_mmio_write()
  arm64: zynqmp: Add support for u-boot.itb generation without ATF

 arch/arm/mach-zynqmp/mkimage_fit_atf.sh | 16 ++++++++++++----
 board/xilinx/zynqmp/zynqmp.c            |  2 +-
 drivers/firmware/firmware-zynqmp.c      |  2 +-
 3 files changed, 14 insertions(+), 6 deletions(-)

-- 
2.25.1

             reply	other threads:[~2020-03-23 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 13:57 Michal Simek [this message]
2020-03-23 13:57 ` [PATCH 1/3] firmware: zynqmp: Enable IPI code calling also in EL3 Michal Simek
2020-03-23 13:57 ` [PATCH 2/3] arm64: zynqmp: Reorder parameters for zynqmp_mmio_write() Michal Simek
2020-03-23 13:58 ` [PATCH 3/3] arm64: zynqmp: Add support for u-boot.itb generation without ATF Michal Simek
2020-04-06 11:08 ` [PATCH 0/3] arm64: zynqmp: Add support for running U-Boot in EL3 again Michal Simek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1584971878.git.michal.simek@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox