devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karan Sanghavi <karansanghvi98@gmail.com>
To: Roger Quadros <rogerq@kernel.org>, Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Karan Sanghavi <karansanghvi98@gmail.com>
Subject: [PATCH] dt-bindings: usb: add missing compatible arraylist
Date: Sun, 22 Sep 2024 17:00:29 +0000	[thread overview]
Message-ID: <ZvBNLRc8xnAoGvoc@Emma> (raw)

Added the vice versa order for compatible property in the yaml file so
that the dtb can parse for the order mentioned in the dts file
k3-am642-sk.dts for ti,j721e-usb.yaml

This is highly ambiguous to me as where exactly the changes needs to be
added is it in the dts file or is the yaml where we have to reverse the
order already mentioned or do we have to add the another order as I have
done ?

Signed-off-by: Karan Sanghavi <karansanghvi98@gmail.com>
---
 Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml
index 95ff9791baea..822653217c43 100644
--- a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml
+++ b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml
@@ -17,6 +17,9 @@ properties:
       - items:
           - const: ti,j721e-usb
           - const: ti,am64-usb
+      - items:
+          - const: ti,am64-usb
+          - const: ti,j721e-usb
 
   reg:
     maxItems: 1
-- 
2.43.0


             reply	other threads:[~2024-09-22 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 17:00 Karan Sanghavi [this message]
2024-09-22 18:51 ` [PATCH] dt-bindings: usb: add missing compatible arraylist Krzysztof Kozlowski
2024-09-23 11:53 ` Roger Quadros
2024-09-28  7:39   ` Karan Sanghavi
2024-09-28  7:58     ` Roger Quadros

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=ZvBNLRc8xnAoGvoc@Emma \
    --to=karansanghvi98@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    /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).