From patchwork Tue Dec 5 10:33:55 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Archit Taneja X-Patchwork-Id: 10092671 X-Patchwork-Delegate: agross@codeaurora.org Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id C395A60348 for ; Tue, 5 Dec 2017 10:34:27 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C1666289ED for ; Tue, 5 Dec 2017 10:34:27 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id B6491291BC; Tue, 5 Dec 2017 10:34:27 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=2.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_HI,T_DKIM_INVALID autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 51CF6289ED for ; Tue, 5 Dec 2017 10:34:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753263AbdLEKe0 (ORCPT ); Tue, 5 Dec 2017 05:34:26 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:37384 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752911AbdLEKeY (ORCPT ); Tue, 5 Dec 2017 05:34:24 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 3678660867; Tue, 5 Dec 2017 10:34:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1512470064; bh=H0pGC433xloJZEzusvSuVehf1XdzRUTcme96avCXYug=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=i8H43eJmpyOo1eu5G4rOQzJJWLy5HoPikHy+rysAVPxaWMS6wT2q0sFddjoZNKzux AXVRFvAsWAo03ZA1UuuONUGVEJYO/hOsYqnewJBq/CYNbE1WgCxqJpfRuenjVLw5GH TbMFgv2qeoe4OoS9xj61Ao3N6O7oJkGufYp4ZWac= Received: from localhost (blr-bdr-fw-01_globalnat_allzones-outside.qualcomm.com [103.229.18.19]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: architt@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 0B2B96081E; Tue, 5 Dec 2017 10:34:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1512470062; bh=H0pGC433xloJZEzusvSuVehf1XdzRUTcme96avCXYug=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=m7JdRrXcCh3ZCqyHZDluXXGjh/DeEejWUyowogihJeyfP1LLlRw5yK/NFLAhEjT6M /t2dgBgAw1sgiwvrlHRKNjeeHUYBGdsYAsQ9dnvz/ObnyjOff5z6Xi7KAFCvDLsLPi ZlQlDxPwnYceE6knnXJNoAuKSp24dyfApd34ehUE= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 0B2B96081E Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=architt@codeaurora.org From: Archit Taneja To: robh+dt@kernel.org Cc: tomi.valkeinen@ti.com, eric@anholt.net, philippe.cornu@st.com, laurent.pinchart@ideasonboard.com, thierry.reding@gmail.com, nickey.yang@rock-chips.com, dri-devel@lists.freedesktop.org, p.zabel@pengutronix.de, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, seanpaul@chromium.org, briannorris@chromium.org, maxime.ripard@free-electrons.com, boris.brezillon@free-electrons.com, a.hajda@samsung.com, Archit Taneja Subject: [RFC 1/2] dt-bindings: mipi-dsi: Add info about peripherals with non-DSI control bus Date: Tue, 5 Dec 2017 16:03:55 +0530 Message-Id: <20171205103356.9917-2-architt@codeaurora.org> X-Mailer: git-send-email 2.15.0 In-Reply-To: <20171205103356.9917-1-architt@codeaurora.org> References: <20171205103356.9917-1-architt@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Add a section that describes dt-bindings for peripherals that support MIPI DSI, but have a different bus as the primary control bus. Add an example for such peripherals. Signed-off-by: Archit Taneja --- .../devicetree/bindings/display/mipi-dsi-bus.txt | 75 ++++++++++++++++++++-- 1 file changed, 68 insertions(+), 7 deletions(-) diff --git a/Documentation/devicetree/bindings/display/mipi-dsi-bus.txt b/Documentation/devicetree/bindings/display/mipi-dsi-bus.txt index 973c27273772..77a7cec15f5b 100644 --- a/Documentation/devicetree/bindings/display/mipi-dsi-bus.txt +++ b/Documentation/devicetree/bindings/display/mipi-dsi-bus.txt @@ -16,7 +16,7 @@ The following assumes that only a single peripheral is connected to a DSI host. Experience shows that this is true for the large majority of setups. DSI host --------- +======== In addition to the standard properties and those defined by the parent bus of a DSI host, the following properties apply to a node representing a DSI host. @@ -30,11 +30,15 @@ Required properties: different value here. See below. DSI peripheral --------------- +============== -Peripherals are represented as child nodes of the DSI host's node. Properties -described here apply to all DSI peripherals, but individual bindings may want -to define additional, device-specific properties. +Peripherals with DSI as control bus +------------------------------------ + +Peripherals with the DSI bus as the primary control path are represented as +child nodes of the DSI host's node. Properties described here apply to all DSI +peripherals, but individual bindings may want to define additional, +device-specific properties. Required properties: - reg: The virtual channel number of a DSI peripheral. Must be in the range @@ -49,9 +53,25 @@ case two alternative representations can be chosen: property is the number of the first virtual channel and the second cell is the number of consecutive virtual channels. -Example -------- +Peripherals with a different control bus +---------------------------------------- + +There are peripherals that have I2C/SPI (or some other non-DSI bus) as the +primary control bus, but are also connected to a DSI bus (mostly for the data +path). Connections between such peripherals and a DSI host can be represented +using the graph bindings [1], [2]. + +[1] Documentation/devicetree/bindings/graph.txt +[2] Documentation/devicetree/bindings/media/video-interfaces.txt +Examples +======== +- (1), (2) and (3) are examples of a DSI host and peripheral on the DSI bus + with different virtual channel configurations. +- (4) is an example of a peripheral on a I2C control bus connected with to + a DSI host using of-graph bindings. + +1) dsi-host { ... @@ -67,6 +87,7 @@ Example ... }; +2) dsi-host { ... @@ -82,6 +103,7 @@ Example ... }; +3) dsi-host { ... @@ -96,3 +118,42 @@ Example ... }; + +4) + i2c-host { + ... + + dsi-bridge@35 { + compatible = "..."; + reg = <0x35>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + ... + + port@0 { + bridge_mipi_in: endpoint { + remote-endpoint = <&host_mipi_out>; + }; + }; + }; + }; + }; + + dsi-host { + ... + + ports { + #address-cells = <1>; + #size-cells = <0>; + ... + + port@0 { + host_mipi_out: endpoint { + remote-endpoint = <&bridge_mipi_in>; + }; + }; + }; + };