[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHQ1cqF_SW16_cvxpDmn6kYoLQDy7CBRfkftUs=u7gR8SQ=MTw@mail.gmail.com>
Date: Mon, 25 Nov 2019 05:21:45 -0800
From: Andrey Smirnov <andrew.smirnov@...il.com>
To: Horia Geanta <horia.geanta@....com>
Cc: "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
Aymen Sghaier <aymen.sghaier@....com>,
Vipul Kumar <vipul_kumar@...tor.com>,
Chris Healy <cphealy@...il.com>,
Lucas Stach <l.stach@...gutronix.de>,
Herbert Xu <herbert@...dor.apana.org.au>,
Iuliana Prodan <iuliana.prodan@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH v4 1/6] crypto: caam - RNG4 TRNG errata
On Mon, Nov 25, 2019 at 12:02 AM Horia Geanta <horia.geanta@....com> wrote:
>
> On 11/21/2019 5:56 PM, Andrey Smirnov wrote:
> > The TRNG as used in RNG4, used in CAAM has a documentation issue. The
> I assume the "erratum" consists in RTMCTL[TRNG_ACC] bit
> not being documented, correct?
>
> Is there an ID of the erratum?
> Or at least do you know what parts / SoCs have incorrect documentation?
>
> > effect is that it is possible that the entropy used to instantiate the
> > DRBG may be old entropy, rather than newly generated entropy. There is
> > proper programming guidance, but it is not in the documentation.
> >
> Is the "programming guidance" public?
>
I don't know the answers to any of those questions. I am not the
original author of this change, just ported if from NXP tree because
it seemed important. More than happy to drop this if you think it's
bogus.
Thanks,
Andrey Smirnov
Powered by blists - more mailing lists