On Tue, Sep 02, 2025 at 02:37:40PM +0530, MD Danish Anwar wrote:
quoted hunk ↗ jump to hunk
Extend the Texas Instruments K3 R5F remoteproc device tree bindings to
include a 'rpmsg-eth' subnode.
This extension allows the RPMsg Ethernet to be defined as a subnode of
K3 R5F remoteproc nodes, enabling the configuration of shared memory-based
Ethernet communication between the host and remote processors.
Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
---
.../devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
index a492f74a8608..4dbd708ec8ee 100644
--- a/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
@@ -210,6 +210,12 @@ patternProperties:
should be defined as per the generic bindings in,
Documentation/devicetree/bindings/sram/sram.yaml
+ rpmsg-eth:
+ $ref: /schemas/net/ti,rpmsg-eth.yaml
No, not a separate device. Please read slides from my DT for beginners
talk from OSSE25. This is EXACTLY the case I covered there - what not to
do.
Best regards,
Krzysztof