From: "Michael Walle" <mwalle@kernel.org>
To: "Nishanth Menon" <nm@ti.com>
Cc: "Udit Kumar" <u-kumar1@ti.com>, <trini@konsulko.com>,
<u-boot@lists.denx.de>, <d-gole@ti.com>, <n-francis@ti.com>,
<vigneshr@ti.com>, <m-chawdhry@ti.com>, <kamlesh@ti.com>,
<j-choudhary@ti.com>
Subject: Re: [PATCH] doc: board: ti: Add optee rng support
Date: Fri, 11 Apr 2025 14:47:50 +0200 [thread overview]
Message-ID: <D93TKGBEXZD4.284M59TUI3SHQ@kernel.org> (raw)
In-Reply-To: <20250411124308.ujiyfbtwyrlrx5hf@devalue>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Hi,
> > > J722S has hw rng, which can be used by OPTEE.
> > > So remove option to use SW TRNG by OPTEE.
> > >
> > > Signed-off-by: Udit Kumar <u-kumar1@ti.com>
> > > ---
> > > reference discussion
> > > https://lore.kernel.org/all/20250313144155.2382316-1-mwalle@kernel.org/
> > >
> > > Bootlogs with optee trng
> > > https://gist.github.com/uditkumarti/5f90210b23e67cd4eb6d06a024031ee8#file-gistfile1-txt-L1970
> >
> >
> > I can confirm the TRNG will work on u-boot as well as linux.
> > Thanks!
>
> just curious: Did you have to change .configs for either?
We are using the (arm64) defconfig in linux, so no.
Regarding u-boot, I don't know because we are using our own config
and I had to enable CONFIG_OPTEE there (as well as
CONFIG_OPTEE_SERVICE_DISCOVERY, but that one is default y).
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-04-11 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 13:27 [PATCH] doc: board: ti: Add optee rng support Udit Kumar
2025-04-10 14:24 ` Nishanth Menon
2025-04-10 15:27 ` Dhruva Gole
2025-04-11 12:17 ` Michael Walle
2025-04-11 12:43 ` Nishanth Menon
2025-04-11 12:47 ` Michael Walle [this message]
2025-04-16 14:10 ` Tom Rini
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=D93TKGBEXZD4.284M59TUI3SHQ@kernel.org \
--to=mwalle@kernel.org \
--cc=d-gole@ti.com \
--cc=j-choudhary@ti.com \
--cc=kamlesh@ti.com \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox