From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: Alexandru Gagniuc <mr.nuke.me@gmail.com>, <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v5 2/5] spl: Introduce spl_board_prepare_for_optee() hook
Date: Tue, 27 Jul 2021 11:13:14 +0200 [thread overview]
Message-ID: <7a91f5b2-9fe7-e9c2-e79a-41b80390620f@foss.st.com> (raw)
In-Reply-To: <20210715191927.337676-3-mr.nuke.me@gmail.com>
Hi,
On 7/15/21 9:19 PM, Alexandru Gagniuc wrote:
> OP-TEE requires some particular setup, which is not needed for linux
> or other payloads. Add a hook for platform-specific code to perform
> any OP-TEE related configuration and initialization.
>
> A weak function is used because it is symmetrical to other
> spl_board_prepare_for_*() implementations. A solution to avoid the use
> of weak functions would trivially apply to all these implementations.
> However, re-designing this is beyond the scope of this patch.
>
> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
> Reviewed-by: Tom Rini <trini@konsulko.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> ---
> common/spl/spl.c | 5 +++++
> include/spl.h | 14 ++++++++++++++
> 2 files changed, 19 insertions(+)
Applied to u-boot-stm/master, thanks!
Regards
Patrick
next prev parent reply other threads:[~2021-07-27 9:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 17:43 [PATCH v4 0/5] stm32mp: Enable OP-TEE and TZC support in SPL Alexandru Gagniuc
2021-05-31 17:43 ` [PATCH v4 1/5] spl: mmc: Support OP-TEE payloads in Falcon mode Alexandru Gagniuc
2021-07-15 18:27 ` Patrick DELAUNAY
2021-07-15 19:11 ` Alex G.
2021-07-15 19:19 ` [PATCH v5 0/5] stm32mp: Enable OP-TEE and TZC support in SPL Alexandru Gagniuc
2021-07-15 19:19 ` [PATCH v5 1/5] spl: mmc: Support OP-TEE payloads in Falcon mode Alexandru Gagniuc
2021-07-27 9:12 ` Patrick DELAUNAY
2021-07-15 19:19 ` [PATCH v5 2/5] spl: Introduce spl_board_prepare_for_optee() hook Alexandru Gagniuc
2021-07-27 9:13 ` Patrick DELAUNAY [this message]
2021-07-15 19:19 ` [PATCH v5 3/5] arm: stm32mp: Implement support for TZC 400 controller Alexandru Gagniuc
2021-07-27 9:14 ` Patrick DELAUNAY
2021-07-15 19:19 ` [PATCH v5 4/5] stm32mp1: spl: Configure TrustZone controller for OP-TEE Alexandru Gagniuc
2021-07-27 9:14 ` Patrick DELAUNAY
2021-07-15 19:19 ` [PATCH v5 5/5] ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb Alexandru Gagniuc
2021-07-27 9:15 ` Patrick DELAUNAY
2021-07-25 15:08 ` [PATCH v5 0/5] stm32mp: Enable OP-TEE and TZC support in SPL Alex G.
2021-05-31 17:43 ` [PATCH v4 2/5] spl: Introduce spl_board_prepare_for_optee() hook Alexandru Gagniuc
2021-05-31 17:43 ` [PATCH v4 3/5] arm: stm32mp: Implement support for TZC 400 controller Alexandru Gagniuc
2021-05-31 17:43 ` [PATCH v4 4/5] stm32mp1: spl: Configure TrustZone controller for OP-TEE Alexandru Gagniuc
2021-07-08 13:23 ` Patrice CHOTARD
2021-07-09 9:03 ` Patrick DELAUNAY
2021-05-31 17:43 ` [PATCH v4 5/5] ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb Alexandru Gagniuc
2021-06-01 15:02 ` Patrick DELAUNAY
2021-07-06 15:18 ` [PATCH v4 0/5] stm32mp: Enable OP-TEE and TZC support in SPL Alex G.
2021-07-06 15:45 ` Tom Rini
2021-07-06 15:55 ` Alex G.
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=7a91f5b2-9fe7-e9c2-e79a-41b80390620f@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=mr.nuke.me@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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