From: Dhruva Gole <d-gole@ti.com>
To: Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, Vignesh Raghavendra <vigneshr@ti.com>,
Dhruva Gole <d-gole@ti.com>, <nm@ti.com>
Subject: [PATCH 1/2] doc: board: beagle: am62x_beagleplay: Delete SW_PRNG flag for OPTEE
Date: Fri, 1 Dec 2023 15:59:53 +0530 [thread overview]
Message-ID: <20231201102954.47582-2-d-gole@ti.com> (raw)
In-Reply-To: <20231201102954.47582-1-d-gole@ti.com>
Delete the flag CFG_WITH_SOFTWARE_PRNG as it's not necessary/ boot
requirement for this SoC
Signed-off-by: Dhruva Gole <d-gole@ti.com>
---
doc/board/beagle/am62x_beagleplay.rst | 1 -
1 file changed, 1 deletion(-)
diff --git a/doc/board/beagle/am62x_beagleplay.rst b/doc/board/beagle/am62x_beagleplay.rst
index 7784e62b0b71..50d7d3c620d7 100644
--- a/doc/board/beagle/am62x_beagleplay.rst
+++ b/doc/board/beagle/am62x_beagleplay.rst
@@ -63,7 +63,6 @@ Set the variables corresponding to this platform:
# we dont use any extra TFA parameters
unset TFA_EXTRA_ARGS
export OPTEE_PLATFORM=k3-am62x
- export OPTEE_EXTRA_ARGS="CFG_WITH_SOFTWARE_PRNG=y"
.. include:: ../ti/am62x_sk.rst
:start-after: .. am62x_evm_rst_include_start_build_steps
--
2.34.1
next prev parent reply other threads:[~2023-12-01 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:29 [PATCH 0/2] docs: AM62x: Remove SW_PRNG Flag for OPTEE Dhruva Gole
2023-12-01 10:29 ` Dhruva Gole [this message]
2023-12-04 19:29 ` [PATCH 1/2] doc: board: beagle: am62x_beagleplay: Delete SW_PRNG flag " Nishanth Menon
2023-12-05 14:46 ` Andrew Davis
2023-12-05 15:22 ` Nishanth Menon
2023-12-05 16:38 ` Andrew Davis
2023-12-01 10:29 ` [PATCH 2/2] doc: board: ti: am62x_sk: Remove SW_PRNG Flag " Dhruva Gole
2023-12-04 19:30 ` [PATCH 0/2] docs: AM62x: " Nishanth Menon
2023-12-05 5:27 ` Dhruva Gole
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=20231201102954.47582-2-d-gole@ti.com \
--to=d-gole@ti.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.