From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Fabian Pflug <fpg@pengutronix.de>
Subject: [PATCH] common: optee: improve documentation of options
Date: Mon, 2 Jun 2025 16:55:21 +0200 [thread overview]
Message-ID: <20250602145521.2801745-1-a.fatoum@pengutronix.de> (raw)
CONFIG_OPTEE_SIZE and CONFIG_OPTEE_SHM_SIZE have a direct correspondence
to OP-TEE build config options, so point that out in the help text.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Cc: Fabian Pflug <fpg@pengutronix.de>
---
common/Kconfig | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/common/Kconfig b/common/Kconfig
index fe50da8f3084..12982b45c59d 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -1307,6 +1307,7 @@ config OPTEE_SIZE
Size to reserve in main memory for OP-TEE.
Can be larger than the actual size used by OP-TEE, this is used to prevent
barebox from using or speculating into this area.
+ This should be at least as big as CFG_TZDRAM_SIZE in OP-TEE.
config OPTEE_SHM_SIZE
hex
@@ -1315,7 +1316,11 @@ config OPTEE_SHM_SIZE
depends on HAVE_OPTEE
help
Size to reserve in main memory for static OP-TEE shared memory
- communication. Can be used for fixing up the OP-TEE OF node.
+ communication. The OP-TEE shared memory starts directly after
+ the OPTEE TZDRAM region. It should be chosen to be equivalent
+ to CFG_SHMEM_SIZE in OP-TEE.
+
+ This value can be used for fixing up the OP-TEE OF node.
A shared memory size of 0 means that only dynamic shared memory
will be supported for communication with OP-TEE. This is the only
--
2.39.5
next reply other threads:[~2025-06-02 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 14:55 Ahmad Fatoum [this message]
2025-06-03 8:07 ` Ahmad Fatoum
2025-06-03 10:59 Ahmad Fatoum
2025-06-03 11:00 ` Ahmad Fatoum
2025-06-05 6:55 ` Sascha Hauer
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=20250602145521.2801745-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=fpg@pengutronix.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