From: Rob Herring <robh@kernel.org>
To: "Miquel Raynal (Schneider Electric)" <miquel.raynal@bootlin.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jayesh Choudhary <j-choudhary@ti.com>,
"David S. Miller" <davem@davemloft.net>,
Christian Marangi <ansuelsmth@gmail.com>,
Antoine Tenart <atenart@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Pascal EBERHARD <pascal.eberhard@se.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 05/16] dt-bindings: bus: eip150: Describe the EIP-150 container node
Date: Tue, 7 Apr 2026 14:44:49 -0500 [thread overview]
Message-ID: <20260407194449.GA3542959-robh@kernel.org> (raw)
In-Reply-To: <20260327-schneider-v7-0-rc1-crypto-v1-5-5e6ff7853994@bootlin.com>
On Fri, Mar 27, 2026 at 09:09:27PM +0100, Miquel Raynal (Schneider Electric) wrote:
> Part of Inside-Secure's SafeXcel family, the EIP-150 is some kind of
> container node composed of:
> - a public key accelerator,
> - random number generator,
> - an interrupt controller.
>
> It also acts as proxy for the clocks.
>
> Signed-off-by: Miquel Raynal (Schneider Electric) <miquel.raynal@bootlin.com>
> ---
> .../bus/inside-secure,safexcel-eip150.yaml | 58 ++++++++++++++++++++++
> 1 file changed, 58 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/bus/inside-secure,safexcel-eip150.yaml b/Documentation/devicetree/bindings/bus/inside-secure,safexcel-eip150.yaml
> new file mode 100644
> index 000000000000..1b3d83a852f5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/inside-secure,safexcel-eip150.yaml
> @@ -0,0 +1,58 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/bus/inside-secure,safexcel-eip150.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Inside-Secure SafeXcel EIP-150 container
> +
> +maintainers:
> + - Miquel Raynal <miquel.raynal@bootlin.com>
> +
> +description:
> + The EIP-150 is a hardware container, it has its own interrupt
> + controller inside to which a random number generator and a public key
> + accelerator are wired.
> +
> +allOf:
> + - $ref: simple-pm-bus.yaml#
> + - $ref: /schemas/clock/clock-nexus-node.yaml#
Generally, if a schema has 'select: true', you don't reference it as it
has already been applied. And you have to list the properties here
anyways because you need to define how many #clock-cells for example.
> +
> +properties:
> + compatible:
> + items:
> + - const: inside-secure,safexcel-eip150
> + - {} # simple-pm-bus, but not listed here to avoid false select
> +
> + clocks:
> + minItems: 1
Seems to me you are adding this to satisfy simple-pm-bus. Maybe this
should just be simple-bus?
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 1
> +
> + ranges: true
> +
> +patternProperties:
> + "^interrupt-controller@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/interrupt-controller/inside-secure,safexcel-eip201.yaml#
Better to just list a compatible you require. Like this, the schema is
applied twice.
> +
> + "^rng@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/rng/inside-secure,safexcel-eip76.yaml#
> +
> + "^crypto@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/crypto/inside-secure,safexcel-eip28.yaml#
> +
> +required:
> + - compatible
> + - clocks
> + - "#address-cells"
> + - "#size-cells"
> + - ranges
The bus schema requires all these already.
Rob
next prev parent reply other threads:[~2026-04-07 19:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 20:09 [PATCH 00/16] Add support for Inside-Secure EIP-150 crypto block Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 01/16] dt-bindings: clock: Introduce nexus nodes Miquel Raynal (Schneider Electric)
2026-04-07 19:29 ` Rob Herring
2026-03-27 20:09 ` [PATCH 02/16] dt-bindings: interrupt-controller: Describe EIP-201 AIC Miquel Raynal (Schneider Electric)
2026-04-07 19:45 ` Rob Herring (Arm)
2026-03-27 20:09 ` [PATCH 03/16] dt-bindings: rng: Rename the title of the EIP-76 file Miquel Raynal (Schneider Electric)
2026-04-07 19:47 ` Rob Herring (Arm)
2026-03-27 20:09 ` [PATCH 04/16] dt-bindings: crypto: eip28: Describe EIP-28 PKA Miquel Raynal (Schneider Electric)
2026-04-07 19:49 ` Rob Herring
2026-03-27 20:09 ` [PATCH 05/16] dt-bindings: bus: eip150: Describe the EIP-150 container node Miquel Raynal (Schneider Electric)
2026-04-07 19:44 ` Rob Herring [this message]
2026-03-27 20:09 ` [PATCH 06/16] clk: tests: Add clk_parse_clkspec() Kunit testing Miquel Raynal (Schneider Electric)
2026-03-30 14:48 ` Brian Masney
2026-04-01 8:59 ` Miquel Raynal
2026-04-01 13:55 ` Brian Masney
2026-03-27 20:09 ` [PATCH 07/16] clk: tests: Add Kunit testing for of_clk_get_parent_name() Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 08/16] clk: Improve a couple of comments Miquel Raynal (Schneider Electric)
2026-03-30 14:50 ` Brian Masney
2026-03-27 20:09 ` [PATCH 09/16] clk: Use the generic OF phandle parsing in only one place Miquel Raynal (Schneider Electric)
2026-03-30 15:01 ` Brian Masney
2026-04-01 8:49 ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 10/16] clk: Add support for clock nexus dt bindings Miquel Raynal (Schneider Electric)
2026-03-30 15:09 ` Brian Masney
2026-03-30 15:16 ` Brian Masney
2026-04-01 8:47 ` Miquel Raynal
2026-04-01 14:04 ` Brian Masney
2026-03-27 20:09 ` [PATCH 11/16] clk: tests: Add Kunit testing for nexus nodes Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 12/16] irqchip/eip201-aic: Add support for Safexcel EIP-201 AIC Miquel Raynal (Schneider Electric)
2026-03-28 13:10 ` Thomas Gleixner
2026-04-01 9:10 ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 13/16] hwrng: omap: Enable on Renesas RZ/N1D Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 14/16] crypto: Group Inside-Secure IPs together and align the titles Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 15/16] crypto: eip28: Add support for SafeXcel EIP-28 Public Key Accelerator Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 16/16] ARM: dts: renesas: r9a06g032: Describe the EIP-150 block Miquel Raynal (Schneider Electric)
2026-04-07 19:33 ` Rob Herring
2026-03-30 13:33 ` [PATCH 00/16] Add support for Inside-Secure EIP-150 crypto block Geert Uytterhoeven
2026-04-01 9:02 ` Miquel Raynal
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=20260407194449.GA3542959-robh@kernel.org \
--to=robh@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=atenart@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=herbert@gondor.apana.org.au \
--cc=j-choudhary@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=olivia@selenic.com \
--cc=pascal.eberhard@se.com \
--cc=sboyd@kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wsa+renesas@sang-engineering.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