Messages in this thread | | | From | Pankaj Gupta <> | Subject | RE: [PATCH] caam: init-clk based on caam-page0-access | Date | Thu, 27 Jul 2023 07:43:49 +0000 |
| |
> -----Original Message----- > From: Horia Geanta <horia.geanta@nxp.com> > Sent: Monday, July 17, 2023 10:39 PM > To: Pankaj Gupta <pankaj.gupta@nxp.com>; Gaurav Jain > <gaurav.jain@nxp.com>; Varun Sethi <V.Sethi@nxp.com>; Herbert Xu > <herbert@gondor.apana.org.au>; David S . Miller <davem@davemloft.net>; > Iuliana Prodan <iuliana.prodan@nxp.com> > Cc: linux-crypto@vger.kernel.org; linux-kernel@vger.kernel.org; dl-linux-imx > <linux-imx@nxp.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
| |