From: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 2/2] spl: add fixed memory node in target fdt also when loading ATF
Date: Mon, 25 May 2020 22:45:19 +0200 [thread overview]
Message-ID: <4DC02031-4CC0-4CBD-AC1A-4AC5EA2DAFB2@theobroma-systems.com> (raw)
In-Reply-To: <20200525175725.3638830-2-heiko@sntech.de>
> On 25.05.2020, at 19:57, Heiko Stuebner <heiko@sntech.de> wrote:
>
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>
> In a loading chain SPL -> ATF (->OP-TEE) -> U-Boot, ATF and a subsequent
> OP-TEE will re-use the same fdt as the U-Boot target and may need the
> information about usable memory ranges.
>
> Especially OP-TEE needs this to initialize dynamic shared memory
> (the only type U-Boot implements when talking to OP-TEE).
>
> So allow spl_fixup_fdt() to take a fdt_blob argument, falling back to
> the existing CONFIG_SYS_SPL_ARGS_ADDR if needed and call it from the
> ATF path as well.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
Reviewed-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
next prev parent reply other threads:[~2020-05-25 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 17:57 [PATCH v2 1/2] rockchip: spl: do full dram_init instead of only probing Heiko Stuebner
2020-05-25 17:57 ` [PATCH v2 2/2] spl: add fixed memory node in target fdt also when loading ATF Heiko Stuebner
2020-05-25 20:45 ` Philipp Tomsich [this message]
2020-05-31 12:51 ` [PATCH v2 1/2] rockchip: spl: do full dram_init instead of only probing Kever Yang
2020-05-31 13:34 ` Kever Yang
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=4DC02031-4CC0-4CBD-AC1A-4AC5EA2DAFB2@theobroma-systems.com \
--to=philipp.tomsich@theobroma-systems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.