From: John Ernberg <john.ernberg@actia.se>
To: Rob Herring <robh@kernel.org>
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>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Frank Li" <Frank.li@nxp.com>,
"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:37:17 +0000 [thread overview]
Message-ID: <aDgqyF7773LJjjJO@w447anl.localdomain> (raw)
In-Reply-To: <20250528215209.GA862463-robh@kernel.org>
Hi Rob,
On Wed, May 28, 2025 at 04:52:09PM -0500, Rob Herring 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.
> >
> > 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
> > - fsl,sec-v5.0
> > - const: fsl,sec-v4.0
> > - const: fsl,sec-v4.0
> > @@ -77,6 +78,9 @@ properties:
> > interrupts:
> > maxItems: 1
> >
> > + power-domains:
> > + maxItems: 1
> > +
> > fsl,sec-era:
> > description: Defines the 'ERA' of the SEC device.
> > $ref: /schemas/types.yaml#/definitions/uint32
> > @@ -106,7 +110,9 @@ patternProperties:
> > - const: fsl,sec-v5.0-job-ring
> > - const: fsl,sec-v4.0-job-ring
> > - items:
> > - - const: fsl,sec-v5.0-job-ring
> > + - enum:
> > + - fsl,imx8qm-job-ring
> > + - fsl,sec-v5.0-job-ring
> > - const: fsl,sec-v4.0-job-ring
> > - const: fsl,sec-v4.0-job-ring
> >
> > @@ -116,6 +122,9 @@ patternProperties:
> > interrupts:
> > maxItems: 1
> >
> > + power-domains:
> > + maxItems: 1
> > +
> > fsl,liodn:
> > description:
> > Specifies the LIODN to be used in conjunction with the ppid-to-liodn
> > @@ -212,6 +221,40 @@ required:
> > - reg
> > - ranges
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + const: fsl,imx8qm-caam
> > + then:
> > + required:
> > + - power-domains
> > + else:
> > + properties:
> > + power-domains: false
> > +
> > + - if:
>
> This 'if' belongs under the '^jr@[0-9a-f]+$' subschema which will then
> remote a level here.
>
This is what I had in v2 [1], which your bot pointed out is an unexpected
if-statement [2]. Or should I have wrapped it in an allOf: even though it
was a single if:?
jernberg % pip install --upgrade dtschema
Requirement already satisfied: dtschema in ./.venv/lib/python3.13/site-packages (2025.2)
[1]: https://lore.kernel.org/linux-crypto/20250527071552.1424997-4-john.ernberg@actia.se/
[2]: https://lore.kernel.org/linux-crypto/174833819381.3537254.5508047100817417003.robh@kernel.org/
Would you mind also letting me know the command line you run validation
with in the CI? I didn't see the v2 (at first, needed W=1 for that) nor
the v3 complaint in my runs before sending.
Thanks! // John Ernberg
> > + patternProperties:
> > + '^jr@[0-9a-f]+$':
> > + type: object
> > + properties:
> > + compatible:
> > + contains:
> > + const: fsl,imx8qm-job-ring
> > + then:
> > + patternProperties:
> > + '^jr@[0-9a-f]+$':
> > + type: object
> > + required:
> > + - power-domains
> > + else:
> > + patternProperties:
> > + '^jr@[0-9a-f]+$':
> > + type: object
> > + properties:
> > + power-domains: false
> > +
> > additionalProperties: false
> >
> > examples:
> > --
> > 2.49.0
next prev parent reply other threads:[~2025-05-29 9:37 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
2025-05-28 16:30 ` Rob Herring (Arm)
2025-05-28 21:52 ` Rob Herring
2025-05-29 9:37 ` John Ernberg [this message]
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 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 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=aDgqyF7773LJjjJO@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