Linux-OMAP Archive on lore.kernel.org
 help / color / Atom feed
* [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml
@ 2020-09-28 22:51 Suman Anna
  2020-09-30 14:55 ` Rob Herring
  0 siblings, 1 reply; 4+ messages in thread
From: Suman Anna @ 2020-09-28 22:51 UTC (permalink / raw)
  To: Rob Herring
  Cc: Nishanth Menon, Bjorn Andersson, devicetree, linux-remoteproc,
	linux-omap, linux-arm-kernel, Suman Anna

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml
  2020-09-28 22:51 [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml Suman Anna
@ 2020-09-30 14:55 ` Rob Herring
  2020-10-06 15:52   ` Rob Herring
  0 siblings, 1 reply; 4+ messages in thread
From: Rob Herring @ 2020-09-30 14:55 UTC (permalink / raw)
  To: Suman Anna
  Cc: Nishanth Menon, devicetree, linux-remoteproc, Bjorn Andersson,
	linux-omap, linux-arm-kernel

On Mon, Sep 28, 2020 at 05:51:55PM -0500, Suman Anna wrote:
> 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(-)

Reviewed-by: Rob Herring <robh@kernel.org>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml
  2020-09-30 14:55 ` Rob Herring
@ 2020-10-06 15:52   ` Rob Herring
  2020-10-06 16:16     ` Suman Anna
  0 siblings, 1 reply; 4+ messages in thread
From: Rob Herring @ 2020-10-06 15:52 UTC (permalink / raw)
  To: Suman Anna
  Cc: Nishanth Menon, devicetree, linux-remoteproc, Bjorn Andersson,
	linux-omap, linux-arm-kernel

On Wed, Sep 30, 2020 at 09:55:37AM -0500, Rob Herring wrote:
> On Mon, Sep 28, 2020 at 05:51:55PM -0500, Suman Anna wrote:
> > 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(-)
> 
> Reviewed-by: Rob Herring <robh@kernel.org>

I guess this isn't dependent on k3.yaml, so I've applied it.

Rob

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml
  2020-10-06 15:52   ` Rob Herring
@ 2020-10-06 16:16     ` Suman Anna
  0 siblings, 0 replies; 4+ messages in thread
From: Suman Anna @ 2020-10-06 16:16 UTC (permalink / raw)
  To: Rob Herring
  Cc: Nishanth Menon, devicetree, linux-remoteproc, Bjorn Andersson,
	linux-omap, linux-arm-kernel

On 10/6/20 10:52 AM, Rob Herring wrote:
> On Wed, Sep 30, 2020 at 09:55:37AM -0500, Rob Herring wrote:
>> On Mon, Sep 28, 2020 at 05:51:55PM -0500, Suman Anna wrote:
>>> 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(-)
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
> 
> I guess this isn't dependent on k3.yaml, so I've applied it.

Yes, it is independent. Thanks Rob.

regards
Suman


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-28 22:51 [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml Suman Anna
2020-09-30 14:55 ` Rob Herring
2020-10-06 15:52   ` Rob Herring
2020-10-06 16:16     ` Suman Anna

Linux-OMAP Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-omap/0 linux-omap/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-omap linux-omap/ https://lore.kernel.org/linux-omap \
		linux-omap@vger.kernel.org
	public-inbox-index linux-omap

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-omap


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git