From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] crypto/fsl: instantiate all rng state handles
Date: Fri, 26 Jan 2018 02:09:10 +0000 [thread overview]
Message-ID: <534abb50-925f-0809-e048-07486bb474d3@linaro.org> (raw)
In-Reply-To: <20180125131117.21077-1-lukas.auer@aisec.fraunhofer.de>
On 25/01/18 13:11, Lukas Auer wrote:
> Extend the instantiate_rng() function and the corresponding CAAM job
> descriptor to instantiate all RNG state handles. This moves the RNG
> instantiation code in line with the CAAM kernel driver.
>
> Previously, only the first state handle was instantiated. The second one
> was instantiated by the CAAM kernel driver. This works if the kernel
> runs in secure mode, but fails in non-secure mode since the kernel
> driver uses DEC0 directly instead of over the job ring interface.
> Instantiating all RNG state handles in u-boot removes the need for using
> DEC0 in the kernel driver, making it possible to use the CAAM in
> non-secure mode.
>
> Signed-off-by: Lukas Auer <lukas.auer@aisec.fraunhofer.de>
So Lukas this patch along with my series for the job-ring ownership
means we can drop detection of TrustZone in the Linux CAAM driver.
Tested-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
next prev parent reply other threads:[~2018-01-26 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 13:11 [U-Boot] [PATCH] crypto/fsl: instantiate all rng state handles Lukas Auer
2018-01-25 15:53 ` Bryan O'Donoghue
2018-01-25 16:11 ` Bryan O'Donoghue
2018-01-25 16:21 ` Auer, Lukas
2018-01-25 16:53 ` Heinrich Schuchardt
2018-01-26 2:09 ` Bryan O'Donoghue [this message]
2018-02-12 22:40 ` York Sun
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=534abb50-925f-0809-e048-07486bb474d3@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=u-boot@lists.denx.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