[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <575811fd-24ca-409c-8d33-c2152ee401d7@www.fastmail.com>
Date: Thu, 23 Jan 2020 12:23:29 +1030
From: "Andrew Jeffery" <andrew@...id.au>
To: "Oscar A Perez" <linux@...ralgames.com>,
"Joel Stanley" <joel@....id.au>
Cc: "Matt Mackall" <mpm@...enic.com>,
"Herbert Xu" <herbert@...dor.apana.org.au>,
"Rob Herring" <robh+dt@...nel.org>,
"Mark Rutland" <mark.rutland@....com>,
"Linux Crypto Mailing List" <linux-crypto@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
"Linux ARM" <linux-arm-kernel@...ts.infradead.org>,
linux-aspeed <linux-aspeed@...ts.ozlabs.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] hwrng: Add support for ASPEED RNG
> Thanks for reviewing the patch.
>
> The RNG on Aspeed hardware allows eight different modes for combining
> its four internal Ring Oscillators that together generate a stream of
> random bits. However, the timeriomem-rng driver does not allow for mode
> selection so, the Aspeed RNG with this generic driver runs always on
> mode 'seven' (The default value for mode according to the AspeedTech
> datasheets).
>
> I've performed some testings on this Aspeed RNG using the NIST
> Statistical Test Suite (NIST 800-22r1a) and, the results I got show that
> the default mode 'seven' isn't producing the best entropy and linear
> rank when compared against the other modes available on these SOCs. On
> the other hand, the driver that I'm proposing here allows for mode
> selection which would help improve the random output for those looking
> to get the best out of this Aspeed RNG.
Have you published the data and results of this study somewhere? This
really should be mentioned in the commit message as justification for
not using timeriomem-rng.
Andrew
Powered by blists - more mailing lists