From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: Vinod Koul <vinod.koul@linaro.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Mackall <mpm@selenic.com>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org, Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH 3/3] hwrng: msm - Add support for prng v2
Date: Thu, 21 Jun 2018 14:27:10 +0300 [thread overview]
Message-ID: <e39deb02-8fa4-84ac-b33e-d692402189a1@linaro.org> (raw)
In-Reply-To: <20180621101506.rnklbtapvfdev4xb@gondor.apana.org.au>
Hi Herbert,
On 06/21/2018 01:15 PM, Herbert Xu wrote:
> On Thu, Jun 21, 2018 at 12:56:34PM +0300, Stanimir Varbanov wrote:
>>
>>> Is this really a pseudo-RNG? If so it needs to be moved over to
>>> the algif_rng interface.
>>
>> Despite the register name (PRNG_ registers prefix) the IP is using FIPS
>> approved algorithm and we can claim that this is true hardware entropy
>> generator.
>
> Whether your RNG is a PRNG or not has nothing to do with the
> algorithm you use. No algorithm can generate entropy out of thin
> air.
OK, I just wanted to say that it is _not_ PRNG and the register names
gives us wrong impression.
--
regards,
Stan
next prev parent reply other threads:[~2018-06-21 11:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 14:12 [PATCH 0/3]: hwrng: Add support for qcpm v2 hwrng Vinod Koul
2018-06-18 14:12 ` [PATCH 1/3] hwrng: msm - Move hwrng to a table Vinod Koul
2018-06-18 15:58 ` Stephen Boyd
2018-06-18 16:54 ` Vinod
2018-06-18 14:12 ` [PATCH 2/3] dt-bindings: rng: Add new compatible qcom,prng-v2 Vinod Koul
2018-06-18 14:12 ` [PATCH 3/3] hwrng: msm - Add support for prng v2 Vinod Koul
2018-06-18 18:21 ` Bjorn Andersson
2018-06-18 20:24 ` Stephen Boyd
2018-06-19 4:06 ` Vinod
2018-06-19 4:04 ` Vinod
2018-06-19 14:28 ` Herbert Xu
2018-06-20 5:32 ` Vinod
2018-06-20 14:37 ` Herbert Xu
2018-06-20 17:45 ` PrasannaKumar Muralidharan
2018-06-21 4:17 ` Vinod
2018-06-21 9:56 ` Stanimir Varbanov
2018-06-21 10:15 ` Herbert Xu
2018-06-21 11:27 ` Stanimir Varbanov [this message]
2018-06-21 11:53 ` Herbert Xu
2018-06-22 8:27 ` Stanimir Varbanov
2018-06-22 14:38 ` Herbert Xu
2018-06-22 14:48 ` Vinod
2018-06-22 14:50 ` Herbert Xu
[not found] ` <70ED61EB-BD3E-48D1-8B4D-D7835494C035@chronox.de>
2018-06-27 5:08 ` Vinod
2018-06-27 6:13 ` Stephan Mueller
2018-06-27 6:27 ` Vinod
2018-06-27 6:43 ` Stephan Mueller
2018-06-27 7:01 ` Vinod
2018-06-27 7:51 ` Stephan Mueller
2018-06-22 15:33 ` Stanimir Varbanov
2018-06-28 22:04 ` Timur Tabi
2018-06-29 8:37 ` Vinod
2018-07-01 6:27 ` Herbert Xu
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=e39deb02-8fa4-84ac-b33e-d692402189a1@linaro.org \
--to=stanimir.varbanov@linaro.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
/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 NNTP newsgroup(s).