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: 11875219 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.0 required=3.0 tests=BAYES_00,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, 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 1A03BC2D0A3 for ; Mon, 2 Nov 2020 20:37:05 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A9E67206F8 for ; Mon, 2 Nov 2020 20:37:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A9E67206F8 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id E57736E323; Mon, 2 Nov 2020 20:37:00 +0000 (UTC) Received: from mail-ot1-f54.google.com (mail-ot1-f54.google.com [209.85.210.54]) by gabe.freedesktop.org (Postfix) with ESMTPS id A79A76E2ED for ; Mon, 2 Nov 2020 20:36:59 +0000 (UTC) Received: by mail-ot1-f54.google.com with SMTP id i18so9170973ots.0 for ; 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=p6kx7CF410kSinf3zKt3iuilv9xD2GFCrBmiBn4M3GPkXqwLTHbixbWiL+nuLucHLw B8+m4qmcaxE6Q6gNSYDLqwa14EYOD3hD7MmazFdu8OOHyqK19Q3gzBKdPi8K+ZoCzl8C dpNamjhKl+MBOkcXgHkM3jVHO52E25XSnYeppYCYyFVqR3ALZ/3yJsS8p1NB+7wYjLOz CcxWQjt79rkvKKhrv241bKypQuWGnJH6jZbN+PEfpG0Jv4Bvj5l2F6aJbHRjEJ/KVY/k tNFSlj1nwVO5vnuknDB3toR3B6V1gm7PB/bPAe8c8jRVafjupm8LOJhCU4yh84ubhh0n qOJQ== X-Gm-Message-State: AOAM531yjqI1+cmvutRIBaaHMfWa3F91SAH6jA9yRzjshjCpgfGkrGSz mJDH5h1lrKjjHZ1YEYUZFg== 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 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 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: kuninori.morimoto.gx@renesas.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Thierry Reding , Jacopo Mondi , Sam Ravnborg Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" 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 Reviewed-by: Laurent Pinchart --- 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: 11875221 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.0 required=3.0 tests=BAYES_00,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 36EB7C388F9 for ; Mon, 2 Nov 2020 20:37:08 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id CDDBB22245 for ; Mon, 2 Nov 2020 20:37:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CDDBB22245 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id C93A36E334; Mon, 2 Nov 2020 20:37:01 +0000 (UTC) Received: from mail-oi1-f193.google.com (mail-oi1-f193.google.com [209.85.167.193]) by gabe.freedesktop.org (Postfix) with ESMTPS id B70736E328 for ; Mon, 2 Nov 2020 20:37:00 +0000 (UTC) Received: by mail-oi1-f193.google.com with SMTP id j7so15986819oie.12 for ; 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=uiwg/F1oPlt7L+fCI5ZYpQAzc/8FQ/PKEVCR7n8IDxhOZqAkMSALSYtwCl9aw/cXnY OK2rzzH7EOEImkVd7OMMOobdgybzFOWOYiiY3dK5G3+WuL8DpxOf5EAIwHuDEXLTPf4K yMujmzl01SAdikhKqsG3QuxfXyCSdYlnG+RQ08s0HfshFwu5hLVwt2xb9CawXQZw13Mt VHJbGU+6iWRBB9A1GfIM7cOqLe4z8sgGiiRQbM2nPva0kW/b0Z3KObbie6DYSZZRXQUE 4VOOwqrnWg4Z5qq4XZf9oePYHzdcTrwamCcAm6XqFwJP/yu56vUJ0ffzNVVE1uc+QHkt 8nAA== X-Gm-Message-State: AOAM5320/pv0/Yrop+gKSHhtxaYWhy+CzsFM0YxVnaGAWrLQxZeieouj 3DYoUXxfD92Jco1eHzFkOA== 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 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 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: kuninori.morimoto.gx@renesas.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Thierry Reding , Jacopo Mondi , Sam Ravnborg Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" 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: 11875223 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.0 required=3.0 tests=BAYES_00,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 0259EC2D0A3 for ; Mon, 2 Nov 2020 20:37:10 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9CE4020719 for ; Mon, 2 Nov 2020 20:37:09 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9CE4020719 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 5270C6E328; Mon, 2 Nov 2020 20:37:04 +0000 (UTC) Received: from mail-oi1-f195.google.com (mail-oi1-f195.google.com [209.85.167.195]) by gabe.freedesktop.org (Postfix) with ESMTPS id E1BA16E328 for ; Mon, 2 Nov 2020 20:37:01 +0000 (UTC) Received: by mail-oi1-f195.google.com with SMTP id x1so15984977oic.13 for ; 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=jmmM08e7+2WJT1XHOc4zpbulUK7xm6FbcNOeDzrzMKGrxOweV477hvBVyqJ11+r7D/ SqQgI4F/HW14a571RBJoMj03hDQfjy5b2A1looRel+W20qxSQkLuZIfKx3fobS65klH3 amwyKbP1wQ4Bm6Dk9WiKL0rs3QU2SO9vG4N/Mb5xuzu74UTucUoMlIbWuvSiZ5KjKiD9 KqJuGnmIARAh47utGV+jPU6P5cCybugujIDaU3LtvfTReuKIvFWih7SE+CTCLoPdW8wH iQyHyX2Nk58ohkip2p/uKHCQoMOZanQzmw8It4zbpxodaV/BzWncbtsd06EzljpSppDs 7i5g== X-Gm-Message-State: AOAM530ebR7wwn4mAH2TsKUhDvXWf3o6AyWIzvNOOjXhRlaXwO2lA2Dl 6WH9CcW//qzleQ+CWGDu6g== X-Google-Smtp-Source: ABdhPJx6uroqdLoV5D8UzKlIH+axYRNJV35FHtiXCCA2TytPvvByeT1flj+DmvIAJWnKLmiKDTEkiA== 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 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 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: kuninori.morimoto.gx@renesas.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Thierry Reding , Jacopo Mondi , Sam Ravnborg Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" 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 Reviewed-by: Sam Ravnborg Reviewed-by: Laurent Pinchart --- v3: new patch .../devicetree/bindings/display/panel/panel-common.yaml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) -- 2.25.1 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