From: Sinthu Raja <sinthu.raja@mistralsolutions.com>
To: Ohad Ben-Cohen <ohad@wizery.com>,
Rob Herring <robh+dt@kernel.org>, Suman Anna <s-anna@ti.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Sinthu Raja <sinthu.raja@ti.com>
Subject: [PATCH] dt-bindings: remoteproc: k3-dsp: Update example to remove board specific
Date: Tue, 17 Aug 2021 20:50:05 +0530 [thread overview]
Message-ID: <20210817152005.21575-1-sinthu.raja@ti.com> (raw)
From: Sinthu Raja <sinthu.raja@ti.com>
The example includes a board-specific compatible property, but developers
need to add the board name each time when a new board is added to the K3
J721E SoC list. This grows the compatible string-list. So, drop the
board-specific compatible string and add cbass_main as a parent node to
avoid parent node and child node address-cells mismatch error.
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
---
.../devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml
index 6070456a7b67..905b8798d4c4 100644
--- a/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml
@@ -132,10 +132,8 @@ required:
unevaluatedProperties: false
examples:
- - |
- / {
- model = "Texas Instruments K3 J721E SoC";
- compatible = "ti,j721e";
+ - |+
+ cbass_main {
#address-cells = <2>;
#size-cells = <2>;
--
2.31.1
next reply other threads:[~2021-08-17 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 15:20 Sinthu Raja [this message]
2021-08-17 18:17 ` Rob Herring
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=20210817152005.21575-1-sinthu.raja@ti.com \
--to=sinthu.raja@mistralsolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=sinthu.raja@ti.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
all inboxes | Powered by JetHome®