From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
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>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Shenwei Wang <shenwei.wang@nxp.com>
Cc: 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-imx@nxp.com
Subject: Re: (subset) [PATCH v3 1/4] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support
Date: Wed, 22 Oct 2025 10:05:00 +0200 [thread overview]
Message-ID: <ad8195d7-dee5-4f50-96a5-506de4cf15a8@linaro.org> (raw)
In-Reply-To: <176095488745.45867.896865155474758901.b4-ty@linaro.org>
On 20/10/2025 12:08, Krzysztof Kozlowski wrote:
>
> On Thu, 09 Oct 2025 17:27:13 -0500, 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.
>>
>> [...]
>
> Applied, thanks!
>
> [1/4] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support
> (no commit info)
>
This was not applied, I just b4-ty wrong patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-22 8:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 22:27 [PATCH v3 0/4] Enable Remote GPIO over RPMSG on i.MX Platform Shenwei Wang
2025-10-09 22:27 ` [PATCH v3 1/4] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support Shenwei Wang
2025-10-20 10:08 ` (subset) " Krzysztof Kozlowski
2025-10-22 7:58 ` Arnaud POULIQUEN
2025-10-22 8:05 ` Krzysztof Kozlowski [this message]
2025-10-09 22:27 ` [PATCH v3 2/4] remoteproc: imx_rproc: Populate devices under "rpmsg" subnode Shenwei Wang
2025-10-09 22:27 ` [PATCH v3 3/4] gpio: imx-rpmsg: add imx-rpmsg GPIO driver Shenwei Wang
2025-10-09 22:58 ` Andrew Lunn
2025-10-10 16:31 ` Mathieu Poirier
2025-10-13 13:33 ` Linus Walleij
2025-10-10 18:58 ` Shenwei Wang
2025-10-10 19:31 ` Andrew Lunn
2025-10-13 14:44 ` Shenwei Wang
2025-10-13 14:56 ` Andrew Lunn
2025-10-13 16:04 ` Shenwei Wang
2025-10-13 16:55 ` Andrew Lunn
2025-10-13 18:41 ` Shenwei Wang
2025-10-13 19:14 ` Andrew Lunn
2025-10-09 22:27 ` [PATCH v3 4/4] arm64: dts: imx8ulp: Add rpmsg node under imx_rproc 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=ad8195d7-dee5-4f50-96a5-506de4cf15a8@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--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-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=robh@kernel.org \
--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).