From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/5] spl: Introduce spl_board_prepare_for_optee() hook
Date: Wed, 3 Feb 2021 11:30:26 -0500 [thread overview]
Message-ID: <20210203163026.GS10169@bill-the-cat> (raw)
In-Reply-To: <20210203152111.1972017-2-mr.nuke.me@gmail.com>
On Wed, Feb 03, 2021 at 09:21:08AM -0600, 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.
>
> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
aside from:
> + /* Weak functions are stupid. Get rid of them! */
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210203/224cfd16/attachment.sig>
next prev parent reply other threads:[~2021-02-03 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 15:21 [PATCH 1/5] spl: mmc: Support OP-TEE payloads in Falcon mode Alexandru Gagniuc
2021-02-03 15:21 ` [PATCH 2/5] spl: Introduce spl_board_prepare_for_optee() hook Alexandru Gagniuc
2021-02-03 16:30 ` Tom Rini [this message]
2021-02-03 15:21 ` [PATCH 3/5] arm: stm32mp: Implement support for TZC 400 controller Alexandru Gagniuc
2021-02-03 15:21 ` [PATCH 4/5] stm32mp1: spl: Configure TrustZone controller for OP-TEE Alexandru Gagniuc
2021-02-03 15:21 ` [PATCH 5/5] ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb Alexandru Gagniuc
2021-02-03 16:30 ` [PATCH 1/5] spl: mmc: Support OP-TEE payloads in Falcon mode Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2021-02-04 19:55 Alexandru Gagniuc
2021-02-04 19:55 ` [PATCH 2/5] spl: Introduce spl_board_prepare_for_optee() hook Alexandru Gagniuc
2021-02-07 14:37 ` Simon Glass
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=20210203163026.GS10169@bill-the-cat \
--to=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