From: John Ernberg <john.ernberg@actia.se>
To: Frank Li <Frank.li@nxp.com>
Cc: "Horia Geantă" <horia.geanta@nxp.com>,
"Pankaj Gupta" <pankaj.gupta@nxp.com>,
"Gaurav Jain" <gaurav.jain@nxp.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Thomas Richard" <thomas.richard@bootlin.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 3/4] dt-bindings: crypto: fsl,sec-v4.0: Add power domains for iMX8QM and iMX8QXP
Date: Thu, 29 May 2025 09:42:02 +0000 [thread overview]
Message-ID: <aDgr6Sc-7CafIr_i@w447anl.localdomain> (raw)
In-Reply-To: <aDckaszTLMcUdIiY@lizhi-Precision-Tower-5810>
Hi Frank,
On Wed, May 28, 2025 at 10:57:46AM -0400, Frank Li wrote:
> On Wed, May 28, 2025 at 02:43:07PM +0000, John Ernberg wrote:
> > NXP SoCs like the iMX8QM, iMX8QXP or iMX8DXP use power domains for
> > resource management.
> >
> > Allow specifying them for such SoCs.
>
> suggest comment:
>
> Add compatible string fsl,imx8qm-caam, and allow power-domains for it. Keep
> the same restriction for others.
Ack.
>
> >
> > Signed-off-by: John Ernberg <john.ernberg@actia.se>
> >
> > ---
> >
> > v3:
> > - Fix warnings discovered by Rob Herring's bot
> > - Declare the compatibles correctly (Krzysztof Kozlowski)
> >
> > v2:
> > - Adjust commit message (Frank Li)
> > - Only allow power-domains when compatible with imx8qm (Frank Li)
> > ---
> > .../bindings/crypto/fsl,sec-v4.0.yaml | 45 ++++++++++++++++++-
> > 1 file changed, 44 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml b/Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml
> > index 75afa441e019..a4ada0e2d97c 100644
> > --- a/Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml
> > +++ b/Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml
> > @@ -46,6 +46,7 @@ properties:
> > - items:
> > - enum:
> > - fsl,imx6ul-caam
> > + - fsl,imx8qm-caam
>
> suggest add fsl,imx8qxp-caam, fsl,imx8dxl-caam also
While I know the DXL comes with the CAAM, I don't have access to any boards
with a DXL on it nor the DXL security manual. So I cannot validate any
changes I would make for the DXL variant.
I propose to keep the DXL out of this patch set, is that ok for you?
I'll add a compat for the QXP in V4.
Thanks! // John Ernberg
>
> Frank
next prev parent reply other threads:[~2025-05-29 9:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 14:43 [PATCH v3 0/4] crypto: caam - iMX8QXP support (and related fixes) John Ernberg
2025-05-28 14:43 ` [PATCH v3 3/4] dt-bindings: crypto: fsl,sec-v4.0: Add power domains for iMX8QM and iMX8QXP John Ernberg
2025-05-28 14:57 ` Frank Li
2025-05-29 9:42 ` John Ernberg [this message]
2025-05-28 16:30 ` Rob Herring (Arm)
2025-05-28 21:52 ` Rob Herring
2025-05-29 9:37 ` John Ernberg
2025-05-28 14:43 ` [PATCH v3 1/4] crypto: caam - Prevent crash on suspend with iMX8QM / iMX8ULP John Ernberg
2025-05-28 14:52 ` Frank Li
2025-05-29 9:51 ` John Ernberg
2025-05-28 14:43 ` [PATCH v3 2/4] crypto: caam - Support iMX8QXP and variants thereof John Ernberg
2025-05-28 14:43 ` [PATCH v3 4/4] arm64: dts: freescale: imx8qxp/imx8qm: Add CAAM support John Ernberg
2025-05-28 15:01 ` Frank Li
2025-05-29 9:49 ` John Ernberg
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=aDgr6Sc-7CafIr_i@w447anl.localdomain \
--to=john.ernberg@actia.se \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=thomas.richard@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox