Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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 0/3] dt-bindings: Convert graph bindings to json-schema
Date:   Mon,  2 Nov 2020 14:36:53 -0600
Message-Id: <20201102203656.220187-1-robh@kernel.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Sameer, I wanted to experiment with what the interface for graph users
looks like, so I've tweaked your patch a bit and converted 2 users.

This series converts the DT graph binding to a schema. Users of the graph
binding should reference the schema from 'ports' or 'port' node. Users
will still need to define what each port node is and any additional
properties that appear in port or endpoint nodes.

I'm still considering whether to apply graph.yaml to the dtschema repo
instead. Then I can sync adding it with a meta-schema update to check
for a reference.

Rob

Rob Herring (2):
  dt-bindings: usb-connector: Add reference to graph schema
  dt-bindings: panel: common: Add reference to graph schema

Sameer Pujar (1):
  dt-bindings: Convert graph bindings to json-schema

 .../bindings/connector/usb-connector.yaml     |  10 +-
 .../bindings/display/panel/panel-common.yaml  |   7 +-
 Documentation/devicetree/bindings/graph.txt   | 129 +-----------
 Documentation/devicetree/bindings/graph.yaml  | 199 ++++++++++++++++++
 4 files changed, 209 insertions(+), 136 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/graph.yaml

--
2.25.1