[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<AM9PR04MB8604DB56777FE12C7C3BFBFB95072@AM9PR04MB8604.eurprd04.prod.outlook.com>
Date: Tue, 9 Apr 2024 07:00:51 +0000
From: Pankaj Gupta <pankaj.gupta@....com>
To: Horia Geanta <horia.geanta@....com>, Gaurav Jain <gaurav.jain@....com>,
Varun Sethi <V.Sethi@....com>, 'Herbert Xu' <herbert@...dor.apana.org.au>,
"'David S . Miller'" <davem@...emloft.net>, Iuliana Prodan
<iuliana.prodan@....com>
CC: "'linux-crypto@...r.kernel.org'" <linux-crypto@...r.kernel.org>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>, dl-linux-imx
<linux-imx@....com>
Subject: RE: [PATCH] caam: init-clk based on caam-page0-access
Hi Horia/Gaurav,
Are there any further comments? Please share.
Regards
Pankaj
> -----Original Message-----
> From: Pankaj Gupta
> Sent: Thursday, July 27, 2023 1:14 PM
> To: Horia Geanta <horia.geanta@....com>; Gaurav Jain
> <gaurav.jain@....com>; Varun Sethi <V.Sethi@....com>; Herbert Xu
> <herbert@...dor.apana.org.au>; David S . Miller <davem@...emloft.net>;
> Iuliana Prodan <iuliana.prodan@....com>
> Cc: linux-crypto@...r.kernel.org; linux-kernel@...r.kernel.org; dl-linux-imx
> <linux-imx@....com>
> Subject: RE: [PATCH] caam: init-clk based on caam-page0-access
>
>
>
> > -----Original Message-----
> > From: Horia Geanta <horia.geanta@....com>
> > Sent: Monday, July 17, 2023 10:39 PM
> > To: Pankaj Gupta <pankaj.gupta@....com>; Gaurav Jain
> > <gaurav.jain@....com>; Varun Sethi <V.Sethi@....com>; Herbert Xu
> > <herbert@...dor.apana.org.au>; David S . Miller <davem@...emloft.net>;
> > Iuliana Prodan <iuliana.prodan@....com>
> > Cc: linux-crypto@...r.kernel.org; linux-kernel@...r.kernel.org;
> > dl-linux-imx <linux-imx@....com>
> > Subject: Re: [PATCH] caam: init-clk based on caam-page0-access
> >
> > On 7/10/2023 8:34 AM, Pankaj Gupta wrote:
> > > CAAM clock initialization to be done based on, soc specific info
> > > stored in struct caam_imx_data:
> > > - caam-page0-access flag
> > > - num_clks
> > >
> > Any specific reason for deviating from downstream implementation
> > (based on DT)?
>
> Implementing based on DT will lead to multiple DT entries in the same code
> section:
> - one entry for imx8ulp(fsl,imx8ulp-ele)
> - then for imx8dxl(fsl,imx-scu)
> - then for imx93 (fsl,imx93-ele)
> - Similar entries for future SoC as well.
>
> Hence, followed this approach.
>
> > https://github.com/nxp-imx/linux-imx/blob/lf-6.1.1-
> > 1.0.1/drivers/crypto/caam/ctrl.c#L911
> >
> > Thanks,
> > Horia
Powered by blists - more mailing lists