From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751651AbdJZExk (ORCPT ); Thu, 26 Oct 2017 00:53:40 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:45014 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750884AbdJZExh (ORCPT ); Thu, 26 Oct 2017 00:53:37 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org AF53F6034E 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 Subject: Re: [PATCH v3 5/6] dt-bindings: add the rockchip, dual-channel for dw-mipi-dsi To: Nickey Yang , mark.yao@rock-chips.com, robh+dt@kernel.org, heiko@sntech.de, mark.rutland@arm.com, airlied@linux.ie Cc: hl@rock-chips.com, zyw@rock-chips.comg, briannorris@chromium.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-rockchip@lists.infradead.org, xbl@rock-chips.com References: <1508903463-7254-1-git-send-email-nickey.yang@rock-chips.com> <1508903463-7254-5-git-send-email-nickey.yang@rock-chips.com> From: Archit Taneja Message-ID: <816a1d2d-d213-709d-f357-63e7c5248ad3@codeaurora.org> Date: Thu, 26 Oct 2017 10:23:29 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <1508903463-7254-5-git-send-email-nickey.yang@rock-chips.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/25/2017 09:21 AM, Nickey Yang wrote: > Configure dsi slave channel when driving a panel > which needs 2 DSI links. > > Signed-off-by: Nickey Yang > --- > .../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt b/Documentation/devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt > index 6bb59ab..a2bea22 100644 > --- a/Documentation/devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt > +++ b/Documentation/devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt > @@ -19,6 +19,8 @@ Optional properties: > - power-domains: a phandle to mipi dsi power domain node. > - resets: list of phandle + reset specifier pairs, as described in [3]. > - reset-names: string reset name, must be "apb". > +- rockchip,dual-channel: phandle to a 2nd DSI channel, useful as a slave > +channel when driving a panel which needs 2 DSI links. The example below is how dual DSI bindings could look like. Let me know what you think of it. If both DSI outputs drive the same device (i.e, point to the same panel DT node), then I think it's reasonable enough to assume that the DSIs are operating in a 'dual-channel' mode. That being said, we still need DT to describe which of the DSIs generates the clock for both the channels. This is done with the 'clock-master' DT binding. Thanks, Archit mipi_dsi: mipi@ff960000 { ... ... clock-master; /* implies that this DSI instance drivers the clock * for both the DSIs. */ ports { mipi_in: port { ... ... }; /* add extra output ports for both DSIs */ mipi_out: port { mipi_panel_out: endpoint { remote-endpoint = <&panel_in_channel0>; }; }; }; panel { ... ... /* * panel node can describe its input ports, if both the DSIs output * ports are connected to the same device (i.e, the same DSI panel), * we can assume that the DSIs need to operate in dual DSI mode */ ports { ... port@0 { panel_in_channel0: endpoint { remote-endpoint = <&mipi_panel_out>; }; }; port@1 { panel_in_channel1: endpoint { remote-endpoint = <&mipi1_panel_out>; }; }; }; }; }; mipi_dsi1: mipi@ff968000 { ... ... ports { mipi1_in: port { ... ... }; mipi1_out: port { mipi1_panel_out: endpoint { remote-endpoint = <&panel_in_channel1>; }; }; }; }; > > [1] Documentation/devicetree/bindings/clock/clock-bindings.txt > [2] Documentation/devicetree/bindings/media/video-interfaces.txt > -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project