From: Ryan Eatmon <reatmon@ti.com>
To: Kamlesh Gurudasani <kamlesh@ti.com>, <vigneshr@ti.com>,
<praneeth@ti.com>, <afd@ti.com>, <m-chawdhry@ti.com>,
<denys@konsulko.com>
Cc: <meta-ti@lists.yoctoproject.org>, <vibhore@ti.com>, <vishalm@ti.com>
Subject: Re: [PATCH v3] optee-os: Enable OP-TEE TRNG in AM62X and AM62PX
Date: Wed, 8 Nov 2023 08:43:57 -0600 [thread overview]
Message-ID: <9b081e68-3412-49cc-9477-e3dcc6ce497e@ti.com> (raw)
In-Reply-To: <20231106-enable-trng-v3-1-e93d7d41ccd4@ti.com>
On 11/8/2023 8:35 AM, Kamlesh Gurudasani wrote:
> Enable TRNG in AM62X and AM62PX, as bugs related to TRNG has been fixed now.
>
> TF-A fix:
> https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=d7a7135d32a8c7da004c0c19b75bd4e2813f9759
>
> OP-TEE fix:
> https://github.com/OP-TEE/optee_os/commit/e313f4765fd0478bb66985827441411793433773
>
> Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
> ---
> Changes in V3:
> -updated commit title and message
>
> Changes in V2:
> -updated commit message
> -included changes for AM62p
> ---
> meta-ti-bsp/recipes-security/optee/optee-os-ti.inc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> 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..435efced 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-os-ti.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-os-ti.inc
You missed my request on the first patch:
When you send the V2 series, can you base the commit off of the
kirkstone-wip branch. I have applied some changes to the file you are
changing above (renamed it in this case) so your patch would not apply
currently. Thanks.
Right now I cannot apply this patch as I have already accepted the
renaming patches into the next branch and it is staged for prod release
as soon as CICD passes.
Please rebase your patch on the kirkstone-wip branch and move your
changes to the optee-os-ti-overrides.inc file.
> @@ -6,8 +6,8 @@ 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:am62pxx = " 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_TEE_CORE_LOG_LEVEL=1"
> EXTRA_OEMAKE:append:am62axx = " CFG_TEE_CORE_LOG_LEVEL=1"
>
> do_compile:append:k3() {
>
> ---
> base-commit: d5e768e29b3f8091cbdedb702ff4185f73af4f3d
> change-id: 20231106-enable-trng-e56f79d668e8
>
> Best regards,
--
Ryan Eatmon reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc. - LCPD - MGTS
prev parent reply other threads:[~2023-11-08 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 14:35 [PATCH v3] optee-os: Enable OP-TEE TRNG in AM62X and AM62PX Kamlesh Gurudasani
2023-11-08 14:43 ` Ryan Eatmon [this message]
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=9b081e68-3412-49cc-9477-e3dcc6ce497e@ti.com \
--to=reatmon@ti.com \
--cc=afd@ti.com \
--cc=denys@konsulko.com \
--cc=kamlesh@ti.com \
--cc=m-chawdhry@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@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).