Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220416135412.4109213-1-festevam@gmail.com> <CAOMZO5B3ENSkK0aL+n=cm73--60mVukNtej=LOdx-Xa8XDkV4g@mail.gmail.com>
 <fc7885ef-1771-b047-699b-517c7f015c9b@nxp.com>
In-Reply-To: <fc7885ef-1771-b047-699b-517c7f015c9b@nxp.com>
From:   Fabio Estevam <festevam@gmail.com>
Date:   Mon, 18 Apr 2022 11:47:48 -0300
Message-ID: <CAOMZO5A9HpLvt4_wHx+Agutc=aWM-aDkLiNoEj3MzNGrU6DVng@mail.gmail.com>
Subject: Re: [PATCH v2] crypto: caam - fix i.MX6SX entropy delay value
To:     =?UTF-8?Q?Horia_Geant=C4=83?= <horia.geanta@nxp.com>
Cc:     Herbert Xu <herbert@gondor.apana.org.au>,
        Gaurav Jain <gaurav.jain@nxp.com>,
        Varun Sethi <V.Sethi@nxp.com>,
        "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" 
        <linux-crypto@vger.kernel.org>, Fabio Estevam <festevam@denx.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, Apr 18, 2022 at 11:43 AM Horia Geant=C4=83 <horia.geanta@nxp.com> w=
rote:

> Someone will need to check whether this solves the issue on i.MX6D,
> the root cause might be different.
>
> Besides this, as Varun said, we should check with the HW team,
> such that the value used for entropy delay is optimal.
> IOW we need TRNG characterization for i.MX6D.

Let's focus on the i.MX6SX for now then.

Please check v3 of the patch that I sent today.