[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DU2PR04MB8630A6F925454E5C007FA3EA95C89@DU2PR04MB8630.eurprd04.prod.outlook.com>
Date: Wed, 11 May 2022 09:16:55 +0000
From: Pankaj Gupta <pankaj.gupta@....com>
To: Ahmad Fatoum <a.fatoum@...gutronix.de>,
Horia Geanta <horia.geanta@....com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>
CC: "kernel@...gutronix.de" <kernel@...gutronix.de>,
Michael Walle <michael@...le.cc>,
James Bottomley <jejb@...ux.ibm.com>,
Jarkko Sakkinen <jarkko@...nel.org>,
Mimi Zohar <zohar@...ux.ibm.com>,
David Howells <dhowells@...hat.com>,
James Morris <jmorris@...ei.org>,
Eric Biggers <ebiggers@...nel.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Jan Luebbe <j.luebbe@...gutronix.de>,
David Gstir <david@...ma-star.at>,
Richard Weinberger <richard@....at>,
Franck Lenormand <franck.lenormand@....com>,
Matthias Schiffer <matthias.schiffer@...tq-group.com>,
Sumit Garg <sumit.garg@...aro.org>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"keyrings@...r.kernel.org" <keyrings@...r.kernel.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-security-module@...r.kernel.org"
<linux-security-module@...r.kernel.org>
Subject: RE: [EXT] [PATCH v9 3/7] crypto: caam - determine whether CAAM
supports blob encap/decap
Hi Ahmad,
Comments in-line.
Regards
Pankaj
> -----Original Message-----
> From: Ahmad Fatoum <a.fatoum@...gutronix.de>
> Sent: Monday, May 9, 2022 6:34 PM
> To: Pankaj Gupta <pankaj.gupta@....com>; Horia Geanta
> <horia.geanta@....com>; Herbert Xu <herbert@...dor.apana.org.au>; David S.
> Miller <davem@...emloft.net>
> Cc: kernel@...gutronix.de; Michael Walle <michael@...le.cc>; James
> Bottomley <jejb@...ux.ibm.com>; Jarkko Sakkinen <jarkko@...nel.org>; Mimi
> Zohar <zohar@...ux.ibm.com>; David Howells <dhowells@...hat.com>; James
> Morris <jmorris@...ei.org>; Eric Biggers <ebiggers@...nel.org>; Serge E.
> Hallyn <serge@...lyn.com>; Jan Luebbe <j.luebbe@...gutronix.de>; David Gstir
> <david@...ma-star.at>; Richard Weinberger <richard@....at>; Franck
> Lenormand <franck.lenormand@....com>; Matthias Schiffer
> <matthias.schiffer@...tq-group.com>; Sumit Garg <sumit.garg@...aro.org>;
> linux-integrity@...r.kernel.org; keyrings@...r.kernel.org; linux-
> crypto@...r.kernel.org; linux-kernel@...r.kernel.org; linux-security-
> module@...r.kernel.org
> Subject: Re: [EXT] [PATCH v9 3/7] crypto: caam - determine whether CAAM
> supports blob encap/decap
>
> Caution: EXT Email
>
> Hello Pankaj,
>
> On Mon, 2022-05-09 at 12:39 +0000, Pankaj Gupta wrote:
> > > - if (ctrlpriv->era < 10)
> > > + comp_params = rd_reg32(&ctrl->perfmon.comp_parms_ls);
> > > + ctrlpriv->blob_present = !!(comp_params & CTPR_LS_BLOB);
> > > +
> > > + if (ctrlpriv->era < 10) {
> > > rng_vid = (rd_reg32(&ctrl->perfmon.cha_id_ls) &
> > > CHA_ID_LS_RNG_MASK) >>
> > > CHA_ID_LS_RNG_SHIFT;
> >
> > Check for AES CHAs for Era < 10, should be added.
>
> Do I need this? I only do this check for Era >= 10, because apparently there are
> Layerscape non-E processors that indicate BLOB support via CTPR_LS_BLOB, but
> fail at runtime. Are there any Era < 10 SoCs that are similarly broken?
>
For non-E variants, it might happen that Blob protocol is enabled, but number of AES CHA are zero.
If the output of below expression is > 0, then only blob_present should be marked present or true.
For era > 10, you handled. But for era < 10, please add the below code.
(rd_reg32(&priv->ctrl->perfmon.cha_num_ls) &
CHA_ID_LS_AES_MASK) >> CHA_ID_LS_AES_SHIFT;
> Cheers,
> Ahmad
Powered by blists - more mailing lists