From: Rob Herring <robh@kernel.org>
To: Shenwei Wang <shenwei.wang@nxp.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Jonathan Corbet <corbet@lwn.net>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-imx@nxp.com
Subject: Re: [PATCH v5 1/5] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support
Date: Wed, 12 Nov 2025 06:53:12 -0600 [thread overview]
Message-ID: <20251112125312.GA1319094-robh@kernel.org> (raw)
In-Reply-To: <20251104203315.85706-2-shenwei.wang@nxp.com>
On Tue, Nov 04, 2025 at 02:33:11PM -0600, Shenwei Wang wrote:
> Remote processors may announce multiple devices (e.g., I2C, GPIO) over
> an RPMSG channel. These devices may require corresponding device tree
> nodes, especially when acting as providers, to supply phandles for their
> consumers.
>
> Define an RPMSG node to work as a container for a group of RPMSG channels
> under the imx_rproc node.
>
> Each subnode within "rpmsg" represents an individual RPMSG channel. The
> name of each subnode corresponds to the channel name as defined by the
> remote processor.
>
> All remote devices associated with a given channel are defined as child
> nodes under the corresponding channel node.
>
> Signed-off-by: Shenwei Wang <shenwei.wang@nxp.com>
> ---
> .../bindings/remoteproc/fsl,imx-rproc.yaml | 123 ++++++++++++++++++
> 1 file changed, 123 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> index 57d75acb0b5e..897a16c4f7db 100644
> --- a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> @@ -84,6 +84,92 @@ properties:
> This property is to specify the resource id of the remote processor in SoC
> which supports SCFW
>
> + rpmsg:
> + type: object
> + additionalProperties: false
> + description:
> + Present a group of RPMSG channel devices.
> +
> + properties:
> + rpmsg-io-channel:
> + type: object
> + additionalProperties: false
> + properties:
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + patternProperties:
> + "gpio@[0-9a-f]+$":
> + type: object
> + unevaluatedProperties: false
> + properties:
> + compatible:
> + enum:
> + - fsl,imx-rpmsg-gpio
> +
> + reg:
> + maxItems: 1
I still don't understand what the numbers for 'reg' mean here. You
explained it and I still don't understand. In any case, it needs to be
explained in the schema.
For example, why do GPIO and I2C each have their own number space?
> +
> + "#gpio-cells":
> + const: 2
> +
> + gpio-controller: true
> +
> + interrupt-controller: true
> +
> + "#interrupt-cells":
> + const: 2
> +
> + required:
> + - compatible
> + - reg
> + - "#gpio-cells"
> + - "#interrupt-cells"
> +
> + allOf:
> + - $ref: /schemas/gpio/gpio.yaml#
> + - $ref: /schemas/interrupt-controller.yaml#
> +
> + required:
> + - '#address-cells'
> + - '#size-cells'
> +
> + rpmsg-i2c-channel:
> + type: object
> + unevaluatedProperties: false
> + properties:
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + patternProperties:
> + "i2c@[0-9a-f]+$":
> + type: object
> + unevaluatedProperties: false
> + properties:
> + compatible:
> + enum:
> + - fsl,imx-rpmsg-i2c
> +
> + reg:
> + maxItems: 1
> +
> + required:
> + - compatible
> + - reg
> +
> + allOf:
> + - $ref: /schemas/i2c/i2c-controller.yaml#
> +
> + required:
> + - '#address-cells'
> + - '#size-cells'
> +
> required:
> - compatible
>
> @@ -146,5 +232,42 @@ examples:
> &mu 3 1>;
> memory-region = <&vdev0buffer>, <&vdev0vring0>, <&vdev0vring1>, <&rsc_table>;
> syscon = <&src>;
> +
> + rpmsg {
> + rpmsg-io-channel {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + gpio@0 {
> + compatible = "fsl,imx-rpmsg-gpio";
> + reg = <0>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + #interrupt-cells = <2>;
> + interrupt-controller;
> + interrupt-parent = <&rpmsg_gpioa>;
> + };
> +
> + gpio@1 {
> + compatible = "fsl,imx-rpmsg-gpio";
> + reg = <1>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + #interrupt-cells = <2>;
> + interrupt-controller;
> + interrupt-parent = <&rpmsg_gpiob>;
> + };
> + };
> +
> + rpmsg-i2c-channel {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + i2c@0 {
> + compatible = "fsl,imx-rpmsg-i2c";
> + reg = <0>;
> + };
> + };
> + };
> };
> ...
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-11-12 12:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 20:33 [PATCH v5 0/5] Enable Remote GPIO over RPMSG on i.MX Platform Shenwei Wang
2025-11-04 20:33 ` [PATCH v5 1/5] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support Shenwei Wang
2025-11-06 18:18 ` Andrew Lunn
2025-11-12 12:53 ` Rob Herring [this message]
2025-11-12 15:36 ` Shenwei Wang
2025-11-04 20:33 ` [PATCH v5 2/5] remoteproc: imx_rproc: Populate devices under "rpmsg" subnode Shenwei Wang
2025-11-06 7:56 ` Peng Fan
2025-11-06 18:23 ` Andrew Lunn
2025-11-04 20:33 ` [PATCH v5 3/5] docs: staging: gpio-rpmsg: gpio over rpmsg bus Shenwei Wang
2025-11-06 19:05 ` Andrew Lunn
2025-11-06 20:40 ` Shenwei Wang
2025-11-06 21:32 ` Andrew Lunn
2025-11-06 23:13 ` Shenwei Wang
2025-11-07 0:31 ` Andrew Lunn
2025-11-07 21:24 ` Shenwei Wang
2025-11-08 17:45 ` Andrew Lunn
2025-11-10 15:24 ` Shenwei Wang
2025-11-10 15:59 ` Andrew Lunn
2025-11-10 16:30 ` Shenwei Wang
2025-11-10 17:58 ` Andrew Lunn
2025-11-11 10:35 ` Linus Walleij
2025-11-11 16:45 ` Shenwei Wang
2025-11-12 13:41 ` Andrew Lunn
2025-11-12 16:31 ` Shenwei Wang
2025-11-12 12:57 ` Rob Herring
2025-11-12 13:35 ` Daniel Baluta
2025-11-12 21:18 ` Randy Dunlap
2025-11-04 20:33 ` [PATCH v5 4/5] gpio: imx-rpmsg: add imx-rpmsg GPIO driver Shenwei Wang
2025-11-06 8:12 ` Peng Fan
2025-11-06 12:31 ` Zhongqiu Han
2025-11-06 17:00 ` Shenwei Wang
2025-11-04 20:33 ` [PATCH v5 5/5] arm64: dts: imx8ulp: Add rpmsg node under imx_rproc Shenwei Wang
2025-11-05 1:12 ` [PATCH v5 0/5] Enable Remote GPIO over RPMSG on i.MX Platform Peng Fan
2025-11-05 10:25 ` Arnaud POULIQUEN
2025-11-05 14:12 ` Shenwei Wang
2025-11-06 10:17 ` Arnaud POULIQUEN
2025-11-06 16:26 ` Shenwei Wang
2025-11-07 17:17 ` Arnaud POULIQUEN
2025-11-07 17:27 ` Andrew Lunn
2025-11-07 22:40 ` Shenwei Wang
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=20251112125312.GA1319094-robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shenwei.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).