From: Gaurav Jain <gaurav.jain@nxp.com>
To: Marek Vasut <marex@denx.de>,
"tharvey@gateworks.com" <tharvey@gateworks.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
Angelo Dureghello <angelo@kernel-space.org>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
Fabio Estevam <festevam@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Michal Simek <michal.simek@amd.com>,
Simon Glass <sjg@chromium.org>, Stefan Roese <sr@denx.de>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Tom Rini <trini@konsulko.com>, Ye Li <ye.li@nxp.com>,
Varun Sethi <V.Sethi@nxp.com>,
Kshitiz Varshney <kshitiz.varshney@nxp.com>
Subject: RE: [EXT] Re: [PATCH 2/3] crypto/fsl: Introduce SPL_FSL_CAAM_RNG
Date: Mon, 29 Apr 2024 09:02:10 +0000 [thread overview]
Message-ID: <AM0PR04MB600444768BFB0DF8114EFAF5E71B2@AM0PR04MB6004.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <94a75eb9-950c-41f0-b9fc-c7d95ecec6c6@denx.de>
Hi Marek
> -----Original Message-----
> From: Marek Vasut <marex@denx.de>
> Sent: Friday, April 26, 2024 9:33 AM
> To: tharvey@gateworks.com
> Cc: u-boot@lists.denx.de; Angelo Dureghello <angelo@kernel-space.org>;
> Emanuele Ghidoli <emanuele.ghidoli@toradex.com>; Fabio Estevam
> <festevam@gmail.com>; Gaurav Jain <gaurav.jain@nxp.com>; Heinrich
> Schuchardt <xypron.glpk@gmx.de>; Michal Simek <michal.simek@amd.com>;
> Simon Glass <sjg@chromium.org>; Stefan Roese <sr@denx.de>; Sughosh Ganu
> <sughosh.ganu@linaro.org>; Svyatoslav Ryhel <clamor95@gmail.com>; Tom Rini
> <trini@konsulko.com>
> Subject: [EXT] Re: [PATCH 2/3] crypto/fsl: Introduce SPL_FSL_CAAM_RNG
>
> Caution: This is an external email. Please take care when clicking links or opening
> attachments. When in doubt, report the message using the 'Report this email'
> button
>
>
> On 4/26/24 2:16 AM, Tim Harvey wrote:
>
> >> diff --git a/drivers/crypto/fsl/Makefile
> >> b/drivers/crypto/fsl/Makefile index 7a2543e16cc..4fbce519a0b 100644
> >> --- a/drivers/crypto/fsl/Makefile
> >> +++ b/drivers/crypto/fsl/Makefile
> >> @@ -6,6 +6,6 @@ obj-y += sec.o
> >> obj-$(CONFIG_FSL_CAAM) += jr.o fsl_hash.o jobdesc.o error.o
> >> obj-$(CONFIG_CMD_BLOB)$(CONFIG_IMX_CAAM_DEK_ENCAP) += fsl_blob.o
> >> obj-$(CONFIG_RSA_FREESCALE_EXP) += fsl_rsa.o
> >> -obj-$(CONFIG_FSL_CAAM_RNG) += rng.o
> >> +obj-$(CONFIG_$(SPL_TPL_)FSL_CAAM_RNG) += rng.o
> >> obj-$(CONFIG_FSL_DCP_RNG) += dcp_rng.o
> >> obj-$(CONFIG_FSL_MFGPROT) += fsl_mfgprot.o
> >> --
> >> 2.43.0
> >>
> >
> > Marek,
>
> Hi,
>
> > Thanks - this series does solve the issue I am seeing in the SPL when
> > enabling DM_RNG. Is this going to cause an issue for people who expect
> > it to be currently enabled and now have to manually enable it?
>
> That's a good question. If I do '$ git grep FSL_CAAM_RNG' , there seem to be no
> users, so I don't think we need to worry here, right ?
>
> With SPL_DM_RNG i.e. 1/3 I am a bit more concerned. But, looking at the users
> that enable DM_RNG, I am not seeing any obvious ones that would require
> SPL_DM_RNG too. What do you think ?
FSL_CAAM_RNG is enabled based on DM_RNG. This patch will disable the build of drivers/crypto/fsl/rng.c in SPL.
Regards
Gaurav Jain
next prev parent reply other threads:[~2024-04-29 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 23:02 [PATCH 1/3] rng: Introduce SPL_DM_RNG Marek Vasut
2024-04-25 23:02 ` [PATCH 2/3] crypto/fsl: Introduce SPL_FSL_CAAM_RNG Marek Vasut
2024-04-26 0:16 ` Tim Harvey
2024-04-26 4:03 ` Marek Vasut
2024-04-26 14:39 ` Heinrich Schuchardt
2024-04-26 17:29 ` Marek Vasut
2024-04-26 17:34 ` Tim Harvey
2024-04-26 19:31 ` Heinrich Schuchardt
2024-04-29 9:02 ` Gaurav Jain [this message]
2024-04-29 12:32 ` [EXT] " Marek Vasut
2024-04-25 23:02 ` [PATCH 3/3] crypto/fsl: Differentiate between CAAM and DCP in Kconfig entry Marek Vasut
2024-05-05 19:12 ` [PATCH 1/3] rng: Introduce SPL_DM_RNG Fabio Estevam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM0PR04MB600444768BFB0DF8114EFAF5E71B2@AM0PR04MB6004.eurprd04.prod.outlook.com \
--to=gaurav.jain@nxp.com \
--cc=V.Sethi@nxp.com \
--cc=angelo@kernel-space.org \
--cc=clamor95@gmail.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=festevam@gmail.com \
--cc=kshitiz.varshney@nxp.com \
--cc=marex@denx.de \
--cc=michal.simek@amd.com \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=sughosh.ganu@linaro.org \
--cc=tharvey@gateworks.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=ye.li@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.