linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Nishanth Menon <nm@ti.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	<devicetree@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>,
	<linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Suman Anna <s-anna@ti.com>
Subject: [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml
Date: Mon, 28 Sep 2020 17:51:55 -0500	[thread overview]
Message-ID: <20200928225155.12432-1-s-anna@ti.com> (raw)

Update the AM65x HwSpinlock example to fix couple of warnings
that started showing up after the conversion of K3 bindings to
YAML format in commit 66e06509aa37 ("dt-bindings: arm: ti:
Convert K3 board/soc bindings to DT schema").

 compatible: ['ti,am654'] is not valid under any of the given schemas (Possible causes of the failure):
 compatible: ['ti,am654'] is too short
 compatible:0: 'ti,am654' is not one of ['ti,am654-evm']

Also, fix one of the node names while at this.

Signed-off-by: Suman Anna <s-anna@ti.com>
---
 .../devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml        | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml b/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml
index 2765758d95e1..ac35491a6f65 100644
--- a/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml
+++ b/Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml
@@ -49,7 +49,7 @@ examples:
     / {
         /* K3 AM65x SoCs */
         model = "Texas Instruments K3 AM654 SoC";
-        compatible = "ti,am654";
+        compatible = "ti,am654-evm", "ti,am654";
         #address-cells = <2>;
         #size-cells = <2>;
 
@@ -60,7 +60,7 @@ examples:
             ranges = <0x00 0x00100000 0x00 0x00100000 0x00 0x00020000>, /* ctrl mmr */
                      <0x00 0x30800000 0x00 0x30800000 0x00 0x0bc00000>; /* Main NavSS */
 
-            main_navss@30800000 {
+            bus@30800000 {
                 compatible = "simple-mfd";
                 #address-cells = <2>;
                 #size-cells = <2>;
-- 
2.28.0


             reply	other threads:[~2020-09-28 23:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 22:51 Suman Anna [this message]
2020-09-30 14:55 ` Rob Herring
2020-10-06 15:52   ` Rob Herring
2020-10-06 16:16     ` Suman Anna

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=20200928225155.12432-1-s-anna@ti.com \
    --to=s-anna@ti.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --subject='Re: [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml' \
    /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

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).