From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Brezillon Subject: Re: [PATCH v2 2/2] dt-bindings: drm/bridge: Document Cadence DSI bridge bindings Date: Mon, 19 Jun 2017 12:12:31 +0200 Message-ID: <20170619121231.5ac1fc95@bbrezillon> References: <1496405096-18275-1-git-send-email-boris.brezillon@free-electrons.com> <1496405096-18275-2-git-send-email-boris.brezillon@free-electrons.com> <60f8b8ec-c83b-0609-c5e5-44b3f9302808@codeaurora.org> <20170606113545.3a9ab2d0@bbrezillon> <902ba6cf-4125-fac6-62dd-6b6198f541f3@ti.com> <20170606144810.1efa0c79@bbrezillon> <9ca829e6-4696-7c3a-aed3-6a2af3161557@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andrzej Hajda Cc: Tomi Valkeinen , Mark Rutland , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Cyprian Wronka , Pawel Moll , Ian Campbell , Simon Hatliff , dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org, Richard Sproul , Alan Douglas , Rob Herring , Kumar Gala , Maxime Ripard , Thomas Petazzoni , Neil Webb , Archit Taneja List-Id: devicetree@vger.kernel.org On Tue, 13 Jun 2017 11:02:47 +0200 Andrzej Hajda wrote: > Hi, > > Just spotted this thread. > > On 06.06.2017 14:58, Tomi Valkeinen wrote: > > On 06/06/17 15:48, Boris Brezillon wrote: > > > >> Okay. Thanks for the clarification. Can you confirm that this version > >> is correct? > >> > >> dsi@xxx { > >> #address-cells = <1>; > >> #size-cells = <0>; > >> > >> ports { > >> #address-cells = <1>; > >> #size-cells = <0>; > >> dpi_in: port@0 { > >> reg = <0>; > >> #address-cells = <1>; > >> #size-cells = <0>; > >> > >> endpoint@0 { > >> remote-endpoint = <&dpi_out>; > >> }; > >> }; > >> > >> dsi_out: port@1 { > >> reg = <1>; > >> #address-cells = <1>; > >> #size-cells = <0>; > >> > >> dsi_out_vc0: endpoint@0 { > >> reg = <0>; > >> remote-endpoint = <&dsi_panel0_in>; > >> }; > >> > >> dsi_out_vc1: endpoint@1 { > >> reg = <1>; > >> remote-endpoint = <&dsi_panel1_in>; > >> }; > >> }; > >> }; > >> > >> panel@0 { > >> compatible = "..."; > >> reg = <0>; > >> #address-cells = <1>; > >> #size-cells = <0>; > >> > >> port@0 { > >> #address-cells = <1>; > >> #size-cells = <0>; > >> reg = <0>; > >> > >> dsi_panel0_in: endpoint@0 { > >> reg = <0>; > >> remote-endpoint = <&dsi_out_vc0>; > >> }; > >> }; > >> }; > >> > >> panel@1 { > >> compatible = "..."; > >> reg = <1>; > >> #address-cells = <1>; > >> #size-cells = <0>; > >> > >> port@0 { > >> #address-cells = <1>; > >> #size-cells = <0>; > >> reg = <0>; > >> > >> dsi_panel1_in: endpoint@0 { > >> reg = <0>; > >> remote-endpoint = <&dsi_out_vc1>; > >> }; > >> }; > >> }; > >> }; > >> > > Looks correct to me. I think it can be a bit shorter though: > > > > - You don't need #address-cells and #size-cells for all. I think those > > are inherited from the parent. > > - If there's just one port and one endpoint, you can leave the 'reg' > > out, as it's considered to be 0 by default. > > > > So for the panel, you can have just: > > > > port { > > dsi_panel1_in: endpoint { > > remote-endpoint = <&dsi_out_vc1>; > > }; > > }; > > In case DSI bus is used to both control and sending video signal you can > skip video links from dsi-host to dsi-child, so nodes can look like: > > > dsi@xxx { > #address-cells = <1>; > #size-cells = <0>; > > ports { > #address-cells = <1>; > #size-cells = <0>; > dpi_in: port@0 { > reg = <0>; > #address-cells = <1>; > #size-cells = <0>; > > endpoint@0 { > remote-endpoint = <&dpi_out>; > }; > }; > > }; > > panel@0 { > compatible = "..."; > reg = <0>; > }; > > panel@1 { > compatible = "..."; > reg = <1>; > }; > }; > Does that mean I should make port1 (AKA DSI ouput port) optional? IMHO, it's clearer when these links are explicitly described in the DT, but maybe there are good reasons to keep it implicit for the "control through DSI" case. Tomi, Archit, any opinion on this? Regards, Boris -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html