From: Rob Herring <robh@kernel.org>
To: devicetree@vger.kernel.org, Sameer Pujar <spujar@nvidia.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
kuninori.morimoto.gx@renesas.com,
Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: [PATCH v3 2/3] dt-bindings: usb-connector: Add reference to graph schema
Date: Mon, 2 Nov 2020 14:36:55 -0600 [thread overview]
Message-ID: <20201102203656.220187-3-robh@kernel.org> (raw)
In-Reply-To: <20201102203656.220187-1-robh@kernel.org>
Now that we have a graph schema, reference it from the usb-connector
schema.
Signed-off-by: Rob Herring <robh@kernel.org>
---
v3: new patch
.../devicetree/bindings/connector/usb-connector.yaml | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/connector/usb-connector.yaml b/Documentation/devicetree/bindings/connector/usb-connector.yaml
index 728f82db073d..64f2e1246ddb 100644
--- a/Documentation/devicetree/bindings/connector/usb-connector.yaml
+++ b/Documentation/devicetree/bindings/connector/usb-connector.yaml
@@ -125,11 +125,13 @@ properties:
power dual role.
ports:
- description: OF graph bindings (specified in bindings/graph.txt) that model
- any data bus to the connector unless the bus is between parent node and
- the connector. Since a single connector can have multiple data buses every
- bus has an assigned OF graph port number as described below.
+ $ref: /schemas/graph.yaml#/properties/ports
type: object
+ description: OF graph bindings modeling any data bus to the connector
+ unless the bus is between parent node and the connector. Since a single
+ connector can have multiple data buses every bus has an assigned OF graph
+ port number as described below.
+
properties:
port@0:
type: object
--
2.25.1
next prev parent reply other threads:[~2020-11-02 20:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 20:36 [PATCH v3 0/3] dt-bindings: Convert graph bindings to json-schema Rob Herring
2020-11-02 20:36 ` [PATCH v3 1/3] " Rob Herring
2020-11-05 21:43 ` Sam Ravnborg
2020-11-11 9:51 ` Sameer Pujar
2020-11-11 13:35 ` Rob Herring
2020-11-11 14:00 ` Laurent Pinchart
2020-11-11 14:25 ` Rob Herring
2020-11-11 14:27 ` Laurent Pinchart
2020-11-11 23:03 ` Rob Herring
2020-11-12 7:56 ` Laurent Pinchart
2020-11-12 20:49 ` Rob Herring
2020-11-02 20:36 ` Rob Herring [this message]
2020-11-11 14:01 ` [PATCH v3 2/3] dt-bindings: usb-connector: Add reference to graph schema Laurent Pinchart
2020-11-02 20:36 ` [PATCH v3 3/3] dt-bindings: panel: common: " Rob Herring
2020-11-05 21:46 ` Sam Ravnborg
2020-11-11 14:02 ` Laurent Pinchart
2020-11-03 6:05 ` [PATCH v3 0/3] dt-bindings: Convert graph bindings to json-schema Sameer Pujar
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=20201102203656.220187-3-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacopo+renesas@jmondi.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=sam@ravnborg.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).