From patchwork Mon Nov 2 20:36:54 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Rob Herring \(Arm\)" X-Patchwork-Id: 314542 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, INCLUDES_PATCH, MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 23C3EC5517A for ; Mon, 2 Nov 2020 20:37:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B228922226 for ; Mon, 2 Nov 2020 20:37:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604349429; bh=xVDzAQ0OfeIIc8m12fCSRI1aF2LfHBkDrmnn4YpYvWc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=DTdjjRVFDOYAyPthV2gN4bLlzRYKFFIHjWw426P1gc1y/te/5a5rIgqNEzEtoOZR6 mazOTiAxysYzfg5sYZ8QO2YNLvIgDKfTDxxgj6ewxEufu5D2BYZwBQvyCyfjW8nIPY O1dGqNul0Got5jUSS922cmWyKd728pfG2ebV8GsE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727140AbgKBUhI (ORCPT ); Mon, 2 Nov 2020 15:37:08 -0500 Received: from mail-ot1-f47.google.com ([209.85.210.47]:37076 "EHLO mail-ot1-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725801AbgKBUhB (ORCPT ); Mon, 2 Nov 2020 15:37:01 -0500 Received: by mail-ot1-f47.google.com with SMTP id l36so5895291ota.4; Mon, 02 Nov 2020 12:36:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=E/f8b/7igunu+rdknGPrkDKABiJMLsPgsX/ibrfgyuE=; b=kc/jH4nOO0sdmL4Haqm9O0pz0OLqiAWGLnf2O0p4Mqp/Hm40U4O/+VSVMF7ns1fF89 0QZuBU/PukqcqBapGLkN2eH+nyprxSPfvcZ/qOXa7hYRE836wAu7cL+OMNrh/jQPm4Mr uPNicodsfdcFi6Ydu0NR9oiopS5yElv/P2lbann70dCrdnuwQ1nQcdOlau3ILqBi0A+y jrak/QFBnuJdcTtMSq05SEKQ+4xUYCBHpJB8+kHVJxkaxyAor+EaDnrhUx1ZShX3Z+5o CUiRKPz9zFDr3H5XQbx7slcoVuhhRVxKfBLDerzPEhAgOTqGgrX1JXsH0YTNz6FE6D0w 51BA== X-Gm-Message-State: AOAM5315ls5c2vt8R5Oa2U5dLvT1W1tUIZbFuCrZVi8naGnwRyxHLprH wIuSbx6niR/faNWtzPDmKSL5eRqorg== X-Google-Smtp-Source: ABdhPJyf/s8o41om4q5HEutHixRV/SLqdRJbExtNHML1Yger7QCH8tsfRI6Lo7DxdnBJe4ivuO4ROw== X-Received: by 2002:a9d:6847:: with SMTP id c7mr12821073oto.134.1604349418876; Mon, 02 Nov 2020 12:36:58 -0800 (PST) Received: from xps15.herring.priv (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.googlemail.com with ESMTPSA id z8sm3839151otm.45.2020.11.02.12.36.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Nov 2020 12:36:58 -0800 (PST) From: Rob Herring To: devicetree@vger.kernel.org, Sameer Pujar , Laurent Pinchart Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Thierry Reding , Sam Ravnborg , Philipp Zabel , kuninori.morimoto.gx@renesas.com, Jacopo Mondi Subject: [PATCH v3 1/3] dt-bindings: Convert graph bindings to json-schema Date: Mon, 2 Nov 2020 14:36:54 -0600 Message-Id: <20201102203656.220187-2-robh@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20201102203656.220187-1-robh@kernel.org> References: <20201102203656.220187-1-robh@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org From: Sameer Pujar Convert device tree bindings of graph to YAML format. Currently graph.txt doc is referenced in multiple files and all of these need to use schema references. For now graph.txt is updated to refer to graph.yaml. For users of the graph binding, they should reference to the graph schema from either 'ports' or 'port' property: properties: ports: type: object $ref: graph.yaml#/properties/ports properties: port@0: description: What data this port has ... Or: properties: port: description: What data this port has type: object $ref: graph.yaml#/properties/port Signed-off-by: Sameer Pujar Acked-by: Philipp Zabel Signed-off-by: Rob Herring Reviewed-by: Sam Ravnborg --- v3: - Move port 'reg' to port@* and make required - Make remote-endpoint required - Add 'additionalProperties: true' now required - Fix yamllint warnings Documentation/devicetree/bindings/graph.txt | 129 +----------- Documentation/devicetree/bindings/graph.yaml | 199 +++++++++++++++++++ 2 files changed, 200 insertions(+), 128 deletions(-) create mode 100644 Documentation/devicetree/bindings/graph.yaml -- 2.25.1 diff --git a/Documentation/devicetree/bindings/graph.txt b/Documentation/devicetree/bindings/graph.txt index 0415e2c53ba0..b7818d61cef7 100644 --- a/Documentation/devicetree/bindings/graph.txt +++ b/Documentation/devicetree/bindings/graph.txt @@ -1,128 +1 @@ -Common bindings for device graphs - -General concept ---------------- - -The hierarchical organisation of the device tree is well suited to describe -control flow to devices, but there can be more complex connections between -devices that work together to form a logical compound device, following an -arbitrarily complex graph. -There already is a simple directed graph between devices tree nodes using -phandle properties pointing to other nodes to describe connections that -can not be inferred from device tree parent-child relationships. The device -tree graph bindings described herein abstract more complex devices that can -have multiple specifiable ports, each of which can be linked to one or more -ports of other devices. - -These common bindings do not contain any information about the direction or -type of the connections, they just map their existence. Specific properties -may be described by specialized bindings depending on the type of connection. - -To see how this binding applies to video pipelines, for example, see -Documentation/devicetree/bindings/media/video-interfaces.txt. -Here the ports describe data interfaces, and the links between them are -the connecting data buses. A single port with multiple connections can -correspond to multiple devices being connected to the same physical bus. - -Organisation of ports and endpoints ------------------------------------ - -Ports are described by child 'port' nodes contained in the device node. -Each port node contains an 'endpoint' subnode for each remote device port -connected to this port. If a single port is connected to more than one -remote device, an 'endpoint' child node must be provided for each link. -If more than one port is present in a device node or there is more than one -endpoint at a port, or a port node needs to be associated with a selected -hardware interface, a common scheme using '#address-cells', '#size-cells' -and 'reg' properties is used to number the nodes. - -device { - ... - #address-cells = <1>; - #size-cells = <0>; - - port@0 { - #address-cells = <1>; - #size-cells = <0>; - reg = <0>; - - endpoint@0 { - reg = <0>; - ... - }; - endpoint@1 { - reg = <1>; - ... - }; - }; - - port@1 { - reg = <1>; - - endpoint { ... }; - }; -}; - -All 'port' nodes can be grouped under an optional 'ports' node, which -allows to specify #address-cells, #size-cells properties for the 'port' -nodes independently from any other child device nodes a device might -have. - -device { - ... - ports { - #address-cells = <1>; - #size-cells = <0>; - - port@0 { - ... - endpoint@0 { ... }; - endpoint@1 { ... }; - }; - - port@1 { ... }; - }; -}; - -Links between endpoints ------------------------ - -Each endpoint should contain a 'remote-endpoint' phandle property that points -to the corresponding endpoint in the port of the remote device. In turn, the -remote endpoint should contain a 'remote-endpoint' property. If it has one, it -must not point to anything other than the local endpoint. Two endpoints with -their 'remote-endpoint' phandles pointing at each other form a link between the -containing ports. - -device-1 { - port { - device_1_output: endpoint { - remote-endpoint = <&device_2_input>; - }; - }; -}; - -device-2 { - port { - device_2_input: endpoint { - remote-endpoint = <&device_1_output>; - }; - }; -}; - -Required properties -------------------- - -If there is more than one 'port' or more than one 'endpoint' node or 'reg' -property present in the port and/or endpoint nodes then the following -properties are required in a relevant parent node: - - - #address-cells : number of cells required to define port/endpoint - identifier, should be 1. - - #size-cells : should be zero. - -Optional endpoint properties ----------------------------- - -- remote-endpoint: phandle to an 'endpoint' subnode of a remote device node. - +This file has moved to graph.yaml diff --git a/Documentation/devicetree/bindings/graph.yaml b/Documentation/devicetree/bindings/graph.yaml new file mode 100644 index 000000000000..b56720c5a13e --- /dev/null +++ b/Documentation/devicetree/bindings/graph.yaml @@ -0,0 +1,199 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/graph.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Common bindings for device graphs + +description: | + The hierarchical organisation of the device tree is well suited to describe + control flow to devices, but there can be more complex connections between + devices that work together to form a logical compound device, following an + arbitrarily complex graph. + There already is a simple directed graph between devices tree nodes using + phandle properties pointing to other nodes to describe connections that + can not be inferred from device tree parent-child relationships. The device + tree graph bindings described herein abstract more complex devices that can + have multiple specifiable ports, each of which can be linked to one or more + ports of other devices. + + These common bindings do not contain any information about the direction or + type of the connections, they just map their existence. Specific properties + may be described by specialized bindings depending on the type of connection. + + To see how this binding applies to video pipelines, for example, see + Documentation/devicetree/bindings/media/video-interfaces.txt. + Here the ports describe data interfaces, and the links between them are + the connecting data buses. A single port with multiple connections can + correspond to multiple devices being connected to the same physical bus. + +maintainers: + - Philipp Zabel + +select: false + +properties: + port: + type: object + description: + If there is more than one endpoint node or 'reg' property present in + endpoint nodes then '#address-cells' and '#size-cells' properties are + required. + + properties: + "#address-cells": + const: 1 + + "#size-cells": + const: 0 + + patternProperties: + "^endpoint(@[0-9a-f]+)?$": + type: object + properties: + reg: + maxItems: 1 + + remote-endpoint: + description: | + phandle to an 'endpoint' subnode of a remote device node. + $ref: /schemas/types.yaml#/definitions/phandle + + required: + - remote-endpoint + + ports: + type: object + description: | + If there is more than one port node or 'reg' property present in port + nodes then '#address-cells' and '#size-cells' properties are required. + In such cases all port nodes can be grouped under 'ports' independently + from any other child device nodes a device might have. + + properties: + "#address-cells": + const: 1 + + "#size-cells": + const: 0 + + patternProperties: + "^port(@[0-9a-f]+)?$": + $ref: "#/properties/port" + type: object + + properties: + reg: + maxItems: 1 + + required: + - reg + + + additionalProperties: false + +additionalProperties: true + +examples: + # Organisation of ports and endpoints: + # + # Ports are described by child 'port' nodes contained in the device node. + # Each port node contains an 'endpoint' subnode for each remote device port + # connected to this port. If a single port is connected to more than one + # remote device, an 'endpoint' child node must be provided for each link. + # If more than one port is present in a device node or there is more than + # one endpoint at a port, or a port node needs to be associated with a + # selected hardware interface, a common scheme using '#address-cells', + # '#size-cells' and 'reg' properties is used to number the nodes. + - | + device { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + #address-cells = <1>; + #size-cells = <0>; + reg = <0>; + + endpoint@0 { + reg = <0>; + // ... + }; + endpoint@1 { + reg = <1>; + // ... + }; + }; + + port@1 { + reg = <1>; + + endpoint { + // ... + }; + }; + }; + + # All 'port' nodes can be grouped under an optional 'ports' node, which + # allows to specify #address-cells, #size-cells properties for the 'port' + # nodes independently from any other child device nodes a device might + # have. + - | + device { + // ... + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + #address-cells = <1>; + #size-cells = <0>; + reg = <0>; + // ... + + endpoint@0 { + reg = <0>; + // ... + }; + endpoint@1 { + reg = <1>; + // ... + }; + }; + + port@1 { + #address-cells = <1>; + #size-cells = <0>; + reg = <1>; + // ... + }; + }; + }; + + # Links between endpoints: + # + # Each endpoint should contain a 'remote-endpoint' phandle property that + # points to the corresponding endpoint in the port of the remote device. + # In turn, the remote endpoint should contain a 'remote-endpoint' property. + # If it has one, it must not point to anything other than the local endpoint. + # Two endpoints with their 'remote-endpoint' phandles pointing at each other + # form a link between the containing ports. + - | + device-1 { + port { + device_1_output: endpoint { + remote-endpoint = <&device_2_input>; + }; + }; + }; + + device-2 { + port { + device_2_input: endpoint { + remote-endpoint = <&device_1_output>; + }; + }; + }; + +... From patchwork Mon Nov 2 20:36:55 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Rob Herring \(Arm\)" X-Patchwork-Id: 314543 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, INCLUDES_PATCH, MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B675BC00A89 for ; Mon, 2 Nov 2020 20:37:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 72C5F22245 for ; Mon, 2 Nov 2020 20:37:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604349422; bh=NLEFyrhYfoQ9VdzhYhyhYWlcMc7iIM2r5mnKKOD3hBk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=gOf0P/ENDf6i4LW4WtWBeuJIEmXRaTGAdBWodZrizhKVEgsiy5FwErrckBVwod2el Drouvlg4Wt3ZUgbQk/+d4ys0XfypmH9ix4IiV5Oi0UKTB7JGDbx/ILkMZudSW8XUat 2N3W0MBFcnsPfJT4hAumqgufrZxptgQu7EJRyr+c= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726694AbgKBUhB (ORCPT ); Mon, 2 Nov 2020 15:37:01 -0500 Received: from mail-oi1-f195.google.com ([209.85.167.195]:41278 "EHLO mail-oi1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726470AbgKBUhA (ORCPT ); Mon, 2 Nov 2020 15:37:00 -0500 Received: by mail-oi1-f195.google.com with SMTP id m13so6944575oih.8; Mon, 02 Nov 2020 12:37:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=eBkyOameG65gPdI9hP/LB1y9VakkF5I8ME127+VZVqc=; b=hKQsaJTh/ePz2LirYhSA+uojhFKTY0SFSvdy1jw4XCTn+h6Kn32J9zjkgukAleS10l jQrId8dWAnADMaHlMBLPGgKKqS8snUnBLMC0qj+Dx4TioTv9yG86ZeiXMFz1Dfr7PNn+ Cg5UisdI/isuCkU9lG1rJgTKAzx6/beqcleDd+N1WXrmTVMltj88jEJvYxMYadb4y7gY FrpyCYNr+0S8HOQqGcsL1WbyWyAOHT1eRk6x/7u82qj3YB8kc5IXP0y2YYQVwNs0tO28 OkieQZ8YizsoPtHuB58TBb8qMxmu/JQP8yZ/NRStQsWSBvRGZfREYkjoAvmRz+gf8QbG hf/w== X-Gm-Message-State: AOAM533c1pKzhbXDRHt4eWbMu2Synhfz06j4FRabYj0LsPpUdkUzQcc8 ww4QEAd5DestPIKq66GnN34Ww/VU0g== X-Google-Smtp-Source: ABdhPJza4LmMMzpz+0LH9Gpao9906cuonotrypVydZeajYy0mOHdV3RtSRdJvM/cXR+aDA22TFg5EA== X-Received: by 2002:aca:1012:: with SMTP id 18mr11289075oiq.30.1604349420093; Mon, 02 Nov 2020 12:37:00 -0800 (PST) Received: from xps15.herring.priv (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.googlemail.com with ESMTPSA id z8sm3839151otm.45.2020.11.02.12.36.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Nov 2020 12:36:59 -0800 (PST) From: Rob Herring To: devicetree@vger.kernel.org, Sameer Pujar , Laurent Pinchart Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Thierry Reding , Sam Ravnborg , Philipp Zabel , kuninori.morimoto.gx@renesas.com, Jacopo Mondi Subject: [PATCH v3 2/3] dt-bindings: usb-connector: Add reference to graph schema Date: Mon, 2 Nov 2020 14:36:55 -0600 Message-Id: <20201102203656.220187-3-robh@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20201102203656.220187-1-robh@kernel.org> References: <20201102203656.220187-1-robh@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Now that we have a graph schema, reference it from the usb-connector schema. Signed-off-by: Rob Herring Reviewed-by: Laurent Pinchart --- v3: new patch .../devicetree/bindings/connector/usb-connector.yaml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) -- 2.25.1 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 From patchwork Mon Nov 2 20:36:56 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Rob Herring \(Arm\)" X-Patchwork-Id: 320373 Delivered-To: patch@linaro.org Received: by 2002:a92:7b12:0:0:0:0:0 with SMTP id w18csp4031258ilc; Mon, 2 Nov 2020 12:37:08 -0800 (PST) X-Google-Smtp-Source: ABdhPJzXrgT5Nkx4UyXkAo9c41Bt/MtnnMsPfLS/oulcGTCHzEp+R420lMpXpqLgioYcYokkdQIX X-Received: by 2002:a17:906:6d99:: with SMTP id h25mr16912531ejt.281.1604349428423; Mon, 02 Nov 2020 12:37:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604349428; cv=none; d=google.com; s=arc-20160816; b=pp95/YeBPgm3ficiSdrPD8RD8nIy+5CbuaS80yWDsviW9yKlQ54UxhKgAswB89mZSr 4u7WpaFe2s2LLdSPt0rOJG/xBhMnFYxRxjxL/VvW4MkIkDKNxTJa2dvXu8y53zI2nLkl 03HrqIc6rlLfyGKTH5xziH90Y05ouVm+dXmXG9f0Xv622GGHI2BDNoEZqVTnM59cbkGJ DDYZucNKvlRNXWdgRHu4amAFdG925aN699rPK/QSwae+bVMe0V+Q6niSVRQNQGymFPP1 7wAAz75fyc/jCexwOuCIAtCjVkThWVA3LMH/6YBl+AaJMTfw/b6U2tT+L4s/fLSeD/bP KApg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=eSe0Eyg4T+VVxvIrbRKcVjoJlAgtXIYs2ZOG69Hyme4=; b=cLw6WRhY+DinD/Ew9joyqxYGOrSasrJdJv/U0SzC8Myd7yPe5eBa/KmfO/X0jrqGCI S1ddnwg2YMy3q6EsYuD2pgVNF7nURxV/DoQJqdZW8cVfXxZhHr9WNuo6iVm8hZv2Xcwt PY+uDksE+xwL0w4eAFgDd+AwTXUzlfbVbdIiR64+VMw+1d6alrOvrw2qVO7e5SpqWhRv j8GZXGyXBxkLfCjb+fBzlrU6liHz9wKLxE0jK5Hwml0IwhsbQ4EKOyLL50U4G+Dmyz/E cUo8RCWGL5Jo5INeS+8mtduLM64fzgy4aR2fjJax1U1PuA8FtpH5ZdHS98P/PUyibgK3 zA7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of devicetree-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=devicetree-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y19si12832579eje.341.2020.11.02.12.37.08; Mon, 02 Nov 2020 12:37:08 -0800 (PST) Received-SPF: pass (google.com: domain of devicetree-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of devicetree-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=devicetree-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727216AbgKBUhC (ORCPT + 6 others); Mon, 2 Nov 2020 15:37:02 -0500 Received: from mail-oi1-f193.google.com ([209.85.167.193]:32814 "EHLO mail-oi1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727192AbgKBUhC (ORCPT ); Mon, 2 Nov 2020 15:37:02 -0500 Received: by mail-oi1-f193.google.com with SMTP id s21so16065189oij.0; Mon, 02 Nov 2020 12:37:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=eSe0Eyg4T+VVxvIrbRKcVjoJlAgtXIYs2ZOG69Hyme4=; b=dVZ7F8beIJOxv4Nij3DsmMBV2Ok1MJAD8qBQ8wYTCPgfIfNQZmx8r2VT/Et0jr+Eug knG7m1BG2mmZ7bhIkSZokSc1qZ28V3K8s4PHqDOjDVoajMB5f8Lj4N5MLZtoYOfl3lYI bt5bNIDzgPT0ejKSRoem0ved2lXBDJIq8FWZdrzPEbr2i2CPXl078m/GU3LNfnS41nF2 gflwubhQ6QLf5x1wDKvN33tppUi+fYlKdJQVLGx5kE/r5n2RglNWRO1kCU6Qt3VJ6cTE LPnUfo/sSlXh4+TJoG87wAbqjmatWwljh+8RIkZXNFJvR+2QlH1a95PS+wlBOi1dnKYx +VAw== X-Gm-Message-State: AOAM533vOAwbkrXYp/2mS+AdTb7MxSXiYd8GCAZOKPrW4FkWTDMHKjYp 8nqH2xRMnsY1+BQL9fqVY6s9GNTd1w== X-Received: by 2002:aca:3a46:: with SMTP id h67mr11418122oia.21.1604349421291; Mon, 02 Nov 2020 12:37:01 -0800 (PST) Received: from xps15.herring.priv (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.googlemail.com with ESMTPSA id z8sm3839151otm.45.2020.11.02.12.37.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Nov 2020 12:37:00 -0800 (PST) From: Rob Herring To: devicetree@vger.kernel.org, Sameer Pujar , Laurent Pinchart Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Thierry Reding , Sam Ravnborg , Philipp Zabel , kuninori.morimoto.gx@renesas.com, Jacopo Mondi Subject: [PATCH v3 3/3] dt-bindings: panel: common: Add reference to graph schema Date: Mon, 2 Nov 2020 14:36:56 -0600 Message-Id: <20201102203656.220187-4-robh@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20201102203656.220187-1-robh@kernel.org> References: <20201102203656.220187-1-robh@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Now that we have a graph schema, reference it from the common panel schema. Cc: Thierry Reding Cc: Sam Ravnborg Cc: Laurent Pinchart Signed-off-by: Rob Herring --- v3: new patch .../devicetree/bindings/display/panel/panel-common.yaml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) -- 2.25.1 Reviewed-by: Sam Ravnborg Reviewed-by: Laurent Pinchart diff --git a/Documentation/devicetree/bindings/display/panel/panel-common.yaml b/Documentation/devicetree/bindings/display/panel/panel-common.yaml index cd6dc5461721..a3a72c574213 100644 --- a/Documentation/devicetree/bindings/display/panel/panel-common.yaml +++ b/Documentation/devicetree/bindings/display/panel/panel-common.yaml @@ -68,16 +68,15 @@ properties: # Connectivity port: - type: object + $ref: /schemas/graph.yaml#/properties/port ports: - type: object + $ref: /schemas/graph.yaml#/properties/ports description: Panels receive video data through one or multiple connections. While the nature of those connections is specific to the panel type, the connectivity is expressed in a standard fashion using ports as specified - in the device graph bindings defined in - Documentation/devicetree/bindings/graph.txt. + in the device graph bindings. ddc-i2c-bus: $ref: /schemas/types.yaml#/definitions/phandle