Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp541222ybz; Wed, 22 Apr 2020 03:18:21 -0700 (PDT) X-Google-Smtp-Source: APiQypKbkd9TTud0q7ZXu7locF0zn4WXVDWUFnLLSDFZ6aKxrmQc4EHxqHxyoyfSY9yBZc2Pl2D9 X-Received: by 2002:a17:907:2719:: with SMTP id w25mr3022612ejk.107.1587550700889; Wed, 22 Apr 2020 03:18:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587550700; cv=none; d=google.com; s=arc-20160816; b=I6rFdMdl5V57997j1dvCEJubjPV6wMPf8Gi9m0DnacqkWamNTYGTzcI2FST3mUZ8da URYEcUbzYm6hnnGeCj3rQp93OGZL4RmtDTwCUp6aftldWcJbzLBvC2dQsb/OCRH8SQUi R8p+GCsjKX8u7i8f1cc5CY7YC5xJ+1Cln3G3EszxNKfSBPUSIt8ZNwB/DnbDgq/wsBrS HOuUNIizVSuB2MP6u3Gvnv6/Aqv5JK+n8AJ7bP6kyBvc/ftdanIqSZIfuERJOQ54pTqp G0FOyUvZDjOTw2vLuC5Q/7f6O8ZY4d2dOfaP5MSiQ373yiXgDAV+0RDfClNRWsZCb898 7RfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=lxMVZZDTgmpSwyZoxAjEgYaz+qrSYdlxxw88wWKgatI=; b=QCxdMmkiCTC8NpivWIMJ78wMNoVsFmWC87J5UVrG2JBleFRb1AxIOafeu3J7g2yKe6 N1RgnuGzq8e6IDPPuoj4+bQg7SAvtSbMVFHcZQH2vpziNiEG6ImJaUzdQYWmHfDeBO1l ra8+bp6QT6Ke8TqIKNGr3ayKf/uHg4aFkff0r3/YJp7FyIaZEj8k1qppTSvMyd/t/8U1 WaHKW2uNZohvOGVfL0A8qSbxdr5/AkvdPm10KqUjIrwvW9ucvwrgJ+8wl9xrExoGgt42 Oz1Qjp9jTRppwaHs4MB6AohtwzK6uLy2fj5TPwls9Y7UzitdRF/6CqJgCGhL5g3mgPhg SN2g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j17si3143807edq.404.2020.04.22.03.17.57; Wed, 22 Apr 2020 03:18:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-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 linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728655AbgDVKOq (ORCPT + 99 others); Wed, 22 Apr 2020 06:14:46 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:43946 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729085AbgDVKOj (ORCPT ); Wed, 22 Apr 2020 06:14:39 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: aratiu) with ESMTPSA id 87A342A1A72 From: Adrian Ratiu To: Laurent Pinchart , Adrian Ratiu Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org, Jernej Skrabec , Heiko Stuebner , Jonas Karlman , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Andrzej Hajda , kernel@collabora.com, linux-stm32@st-md-mailman.stormreply.com, linux-imx@nxp.com, Rob Herring , Neil Armstrong , Fabio Estevam , Adrian Pop , Arnaud Ferraris , Sjoerd Simons , Martyn Welch Subject: Re: [PATCH v7 5/8] dt-bindings: display: add i.MX6 MIPI DSI host controller doc In-Reply-To: <20200422010155.GL5983@pendragon.ideasonboard.com> References: <20200421161610.1501827-1-adrian.ratiu@collabora.com> <20200421161610.1501827-6-adrian.ratiu@collabora.com> <20200422005832.GK5983@pendragon.ideasonboard.com> <20200422010155.GL5983@pendragon.ideasonboard.com> Date: Wed, 22 Apr 2020 13:15:41 +0300 Message-ID: <877dy7ker6.fsf@collabora.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 22 Apr 2020, Laurent Pinchart wrote: > Hi Adrian, > Hi Laurent, > On Wed, Apr 22, 2020 at 03:58:33AM +0300, Laurent Pinchart > wrote: >> On Tue, Apr 21, 2020 at 07:16:07PM +0300, Adrian Ratiu wrote: >> > This provides an example DT binding for the MIPI DSI host >> > controller present on the i.MX6 SoC based on Synopsis >> > DesignWare v1.01 IP. Cc: Rob Herring Cc: >> > Neil Armstrong Cc: Fabio Estevam >> > Cc: Laurent Pinchart >> > Cc: >> > devicetree@vger.kernel.org Tested-by: Adrian Pop >> > Tested-by: Arnaud Ferraris >> > Signed-off-by: Sjoerd Simons >> > Signed-off-by: Martyn Welch >> > Signed-off-by: Adrian Ratiu >> > --- Changes since v6: >> > - Added ref to the newly created snps,dw-mipi-dsi.yaml >> > (Laurent) - Moved *-cells properties outside >> > patternProperties (Laurent) - Removed the panel port >> > documentation (Laurent) - Wrapped lines at 80 chars, typo >> > fixes, sort includes (Laurent) >> > Changes since v5: >> > - Fixed missing reg warning (Fabio) - Updated dt-schema and >> > fixed warnings (Rob) >> > Changes since v4: >> > - Fixed yaml binding to pass `make dt_binding_check >> > dtbs_check` and addressed received binding feedback (Rob) >> > Changes since v3: >> > - Added commit message (Neil) - Converted to yaml format >> > (Neil) - Minor dt node + driver fixes (Rob) - Added small >> > panel example to the host controller binding >> > Changes since v2: >> > - Fixed commit tags (Emil) >> > --- >> > .../display/imx/fsl,mipi-dsi-imx6.yaml | 135 >> > ++++++++++++++++++ 1 file changed, 135 insertions(+) create >> > mode 100644 >> > Documentation/devicetree/bindings/display/imx/fsl,mipi-dsi-imx6.yaml >> > diff --git >> > a/Documentation/devicetree/bindings/display/imx/fsl,mipi-dsi-imx6.yaml >> > b/Documentation/devicetree/bindings/display/imx/fsl,mipi-dsi-imx6.yaml >> > new file mode 100644 index 0000000000000..b73e3ae33a852 --- >> > /dev/null +++ >> > b/Documentation/devicetree/bindings/display/imx/fsl,mipi-dsi-imx6.yaml >> > @@ -0,0 +1,135 @@ +# SPDX-License-Identifier: (GPL-2.0-only >> > OR BSD-2-Clause) +%YAML 1.2 +--- +$id: >> > http://devicetree.org/schemas/display/imx/fsl,mipi-dsi-imx6.yaml# >> > +$schema: http://devicetree.org/meta-schemas/core.yaml# + >> > +title: Freescale i.MX6 DW MIPI DSI Host Controller + >> > +maintainers: + - Adrian Ratiu >> > + +description: | + The i.MX6 DSI host controller is a >> > Synopsys DesignWare MIPI DSI v1.01 + IP block with a >> > companion PHY IP. > > I forgot to mention, if there's a companion PHY, shouldn't it be > referenced from the DT bindings ? > I don't think so, that description was copied verbatim from the imx6 ref manual IIRC, the physical layer is the same for MIPI DSI which does TX as for MIPI CSI which does RX, but looking at the ref manual and how drivers are written I don't think it's necessary. This might change if we wanted to unify the DSI and CSI drivers a bit, but considering the scope already associated with this patch series I'm a bit afraid to open a subject like that =) >> > + >> > + These DT bindings follow the Synopsys DW MIPI DSI bindings defined in >> > + Documentation/devicetree/bindings/display/bridge/dw_mipi_dsi.txt with >> > + the following device-specific properties. >> > + >> > +allOf: >> > + - $ref: ../bridge/snps,dw-mipi-dsi.yaml# >> > + >> > +properties: >> > + '#address-cells': >> > + const: 1 >> > + >> > + '#size-cells': >> > + const: 0 >> > + >> > + compatible: >> > + items: >> > + - const: fsl,imx6q-mipi-dsi >> > + - const: snps,dw-mipi-dsi >> > + >> > + reg: >> > + maxItems: 1 >> > + >> > + interrupts: >> > + maxItems: 1 >> > + >> > + clocks: >> > + items: >> > + - description: Module Clock >> > + - description: DSI bus clock >> > + >> > + clock-names: >> > + items: >> > + - const: ref >> > + - const: pclk >> > + >> > + fsl,gpr: >> > + description: >> > + Phandle to the iomuxc-gpr region containing the multiplexer ctrl register. >> > + $ref: /schemas/types.yaml#/definitions/phandle >> > + >> > + ports: >> > + type: object >> > + description: | >> > + A node containing DSI input & output port nodes with endpoint >> > + definitions as documented in >> > + Documentation/devicetree/bindings/media/video-interfaces.txt >> > + Documentation/devicetree/bindings/graph.txt >> > + properties: >> > + port@0: >> > + type: object >> > + description: >> > + DSI input port node, connected to the ltdc rgb output port. >> > + >> > + port@1: >> > + type: object >> > + description: >> > + RGB output port node, connected to a panel or a bridge input port. >> >> Isn't it the other way around, doesn't the bridge take RGB input and >> output DSI ? And to be precise, it's not about RGB, but about the input >> being parallel interface (DSI will also carry RGB). >> >> I would add >> >> required: >> - port@0 >> - port@1 >> >> > + >> > +additionalProperties: false >> > + >> > +patternProperties: >> > + "^panel@[0-3]$": >> > + type: object >> > + >> > +required: >> > + - "#address-cells" >> > + - "#size-cells" >> > + - compatible >> > + - reg >> > + - interrupts >> > + - clocks >> > + - clock-names >> > + - ports >> > + >> > +examples: >> > + - |+ >> > + #include >> > + #include >> > + #include >> > + >> > + dsi: dsi@21e0000 { >> > + #address-cells = <1>; >> > + #size-cells = <0>; >> > + compatible = "fsl,imx6q-mipi-dsi", "snps,dw-mipi-dsi"; >> > + reg = <0x021e0000 0x4000>; >> > + interrupts = <0 102 IRQ_TYPE_LEVEL_HIGH>; >> > + fsl,gpr = <&gpr>; >> > + clocks = <&clks IMX6QDL_CLK_MIPI_CORE_CFG>, >> > + <&clks IMX6QDL_CLK_MIPI_IPG>; >> > + clock-names = "ref", "pclk"; >> > + >> > + ports { >> > + #address-cells = <1>; >> > + #size-cells = <0>; >> >> port@0 is missing. >> >> > + port@1 { >> > + reg = <1>; >> > + dsi_out: endpoint { >> > + remote-endpoint = <&panel_in>; >> > + }; >> > + }; >> > + }; >> > + >> > + panel@0 { >> > + compatible = "sharp,ls032b3sx01"; >> > + reg = <0>; >> > + reset-gpios = <&gpio6 8 GPIO_ACTIVE_LOW>; >> > + ports { >> > + #address-cells = <1>; >> > + #size-cells = <0>; >> > + port@0 { >> > + reg = <0>; >> > + panel_in: endpoint { >> > + remote-endpoint = <&dsi_out>; >> > + }; >> > + }; >> > + }; >> > + }; >> > + }; >> > + >> > +... > > -- > Regards, > > Laurent Pinchart