From: Kamlesh Gurudasani <kamlesh@ti.com>
To: <vigneshr@ti.com>, <praneeth@ti.com>, <u-kumar1@ti.com>,
<afd@ti.com>, <m-chawdhry@ti.com>, <reatmon@ti.com>,
<denys@konsulko.com>
Cc: <meta-ti@lists.yoctoproject.org>, <vibhore@ti.com>,
<vishalm@ti.com>, Kamlesh Gurudasani <kamlesh@ti.com>
Subject: [PATCH] optee-os: Enable OP-TEE TRNG in AM62X
Date: Mon, 6 Nov 2023 16:55:50 +0530 [thread overview]
Message-ID: <20231106-enable-trng-v1-1-59cb0b4f9bcb@ti.com> (raw)
Enable TRNG in AM62X, as bugs related to TRNG has been fixed now.
Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
---
meta-ti-bsp/recipes-security/optee/optee-os-ti.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-bsp/recipes-security/optee/optee-os-ti.inc b/meta-ti-bsp/recipes-security/optee/optee-os-ti.inc
index 91b66a36..d1c15cb2 100644
--- a/meta-ti-bsp/recipes-security/optee/optee-os-ti.inc
+++ b/meta-ti-bsp/recipes-security/optee/optee-os-ti.inc
@@ -6,7 +6,7 @@ inherit ti-secdev
EXTRA_OEMAKE:append:k3 = "${@ ' CFG_CONSOLE_UART='+ d.getVar('OPTEE_K3_USART') if d.getVar('OPTEE_K3_USART') else ''}"
-EXTRA_OEMAKE:append:am62xx = " CFG_WITH_SOFTWARE_PRNG=y CFG_TEE_CORE_LOG_LEVEL=1"
+EXTRA_OEMAKE:append:am62xx = " CFG_TEE_CORE_LOG_LEVEL=1"
EXTRA_OEMAKE:append:am62pxx = " CFG_WITH_SOFTWARE_PRNG=y CFG_TEE_CORE_LOG_LEVEL=1"
EXTRA_OEMAKE:append:am62axx = " CFG_TEE_CORE_LOG_LEVEL=1"
---
base-commit: d5e768e29b3f8091cbdedb702ff4185f73af4f3d
change-id: 20231106-enable-trng-e56f79d668e8
Best regards,
--
Kamlesh Gurudasani <kamlesh@ti.com>
next reply other threads:[~2023-11-06 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 11:25 Kamlesh Gurudasani [this message]
2023-11-06 15:04 ` [PATCH] optee-os: Enable OP-TEE TRNG in AM62X Bajjuri, Praneeth
2023-11-07 8:15 ` Kamlesh Gurudasani
2023-11-07 9:52 ` Vibhore Vardhan
2023-11-07 19:34 ` Ryan Eatmon
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=20231106-enable-trng-v1-1-59cb0b4f9bcb@ti.com \
--to=kamlesh@ti.com \
--cc=afd@ti.com \
--cc=denys@konsulko.com \
--cc=m-chawdhry@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=u-kumar1@ti.com \
--cc=vibhore@ti.com \
--cc=vigneshr@ti.com \
--cc=vishalm@ti.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).