Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2592766ybb; Sun, 12 Apr 2020 09:46:29 -0700 (PDT) X-Google-Smtp-Source: APiQypLLHiW9BKKvIHTC85SwJk420h9SUj5g0C8LZ63AYwFczOJ2APo87HSiUgXp+ENwPDkQSck/ X-Received: by 2002:a37:a3d3:: with SMTP id m202mr2000060qke.338.1586709989382; Sun, 12 Apr 2020 09:46:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586709989; cv=none; d=google.com; s=arc-20160816; b=Im3vnr3iIBkP6xfMCajh0UDucob8CJ6Mmf1EdM3nSjitro7Xoj10E5qa0Wmwujdp8g rN30OD27+gIXHKTbJszCnG3P7Vof0mgo0nJa8BDC6IxQa+BhvOo3I6rcPf2XpY52FitF 9giawGe5XQmnj+YN4LNBL9dHXDDYlw5MpLxshecWQnVd2jt7mL548zp/rut/+mLQNHd2 Y0jNgJ5s+gwTgWTR8bZQEvXxwXbb9tnnTEdQCDixdXbHjb6Rs+YNRvpPDFYNwvJIC/Ta FTWmVz3tWV7+IYz1f5fNDA4IX1F301s+7JPmhaYyp7i5figXUv0CeUrc21IZvv9KwSRC D14Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=92/hZ78HQ3gSYJeWdzFH6a/P494fUAzDOrGNxI3cZuc=; b=M/ObieYtGeb7rKB3PCT83gdpDG5gGr2QlEsVZhBcTcdyhVb3GPZW2mbaMOB1X3pUuB 79mFp72/QHif3Dyl0pr7zA0ZfZm8BRpirXk6NliBrF9AeF0Lt+Euo22qgj4sDLatzzLR uNJRfYOxTFlb0AXOPqX36RlKuyylZrrIZCxVZPOJ/z1T0Ebm0JJGBU8CJcBHbzlxspfN Kk3/O5iwdlNERB57g3rUJcKWuTXGJU3QdmPTAbC4kMndVeEWtihHuyS9M82+mtjJtfpl yAqwjsUD3n7399zzhMeYl6xaTsuuggHB+7xPJV9k0uN1bqz2iplFpygtSGq0l4iriTEK Wy8A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j23si4445741qkl.284.2020.04.12.09.46.12; Sun, 12 Apr 2020 09:46:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727131AbgDLQpG (ORCPT + 99 others); Sun, 12 Apr 2020 12:45:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.18]:54774 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726962AbgDLQpG (ORCPT ); Sun, 12 Apr 2020 12:45:06 -0400 Received: from honk.sigxcpu.org (honk.sigxcpu.org [24.134.29.49]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 42CCBC0A3BF1; Sun, 12 Apr 2020 09:38:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by honk.sigxcpu.org (Postfix) with ESMTP id 5DAB7FB03; Sun, 12 Apr 2020 18:38:38 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at honk.sigxcpu.org Received: from honk.sigxcpu.org ([127.0.0.1]) by localhost (honk.sigxcpu.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KFNyfXJzYr2u; Sun, 12 Apr 2020 18:38:35 +0200 (CEST) Received: by bogon.sigxcpu.org (Postfix, from userid 1000) id 2FCF640601; Sun, 12 Apr 2020 18:38:35 +0200 (CEST) Date: Sun, 12 Apr 2020 18:38:35 +0200 From: Guido =?iso-8859-1?Q?G=FCnther?= To: Laurent Pinchart Cc: David Airlie , Daniel Vetter , Rob Herring , Mark Rutland , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Andrzej Hajda , Neil Armstrong , Jonas Karlman , Jernej Skrabec , Lee Jones , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Robert Chiras , Sam Ravnborg , Arnd Bergmann Subject: Re: [PATCH v11 1/2] dt-bindings: display/bridge: Add binding for NWL mipi dsi host controller Message-ID: <20200412163835.GB4007@bogon.m.sigxcpu.org> References: <147ffc1e4dee3a623e5dca25d84565d386a34112.1586427783.git.agx@sigxcpu.org> <20200410112342.GB4751@pendragon.ideasonboard.com> <20200410124516.GA27532@bogon.m.sigxcpu.org> <20200410125732.GE4751@pendragon.ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200410125732.GE4751@pendragon.ideasonboard.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Laurent, On Fri, Apr 10, 2020 at 03:57:32PM +0300, Laurent Pinchart wrote: > Hi Guido, > > On Fri, Apr 10, 2020 at 02:45:16PM +0200, Guido G?nther wrote: > > On Fri, Apr 10, 2020 at 02:23:42PM +0300, Laurent Pinchart wrote: > > > On Thu, Apr 09, 2020 at 12:42:01PM +0200, Guido G?nther wrote: > > > > The Northwest Logic MIPI DSI IP core can be found in NXPs i.MX8 SoCs. > > > > > > > > Signed-off-by: Guido G?nther > > > > Tested-by: Robert Chiras > > > > Reviewed-by: Rob Herring > > > > Acked-by: Sam Ravnborg > > > > Reviewed-by: Fabio Estevam > > > > --- > > > > .../bindings/display/bridge/nwl-dsi.yaml | 226 ++++++++++++++++++ > > > > 1 file changed, 226 insertions(+) > > > > create mode 100644 Documentation/devicetree/bindings/display/bridge/nwl-dsi.yaml > > > > > > > > diff --git a/Documentation/devicetree/bindings/display/bridge/nwl-dsi.yaml b/Documentation/devicetree/bindings/display/bridge/nwl-dsi.yaml > > > > new file mode 100644 > > > > index 000000000000..8aff2d68fc33 > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/display/bridge/nwl-dsi.yaml > > > > @@ -0,0 +1,226 @@ > > > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > > > +%YAML 1.2 > > > > +--- > > > > +$id: http://devicetree.org/schemas/display/bridge/nwl-dsi.yaml# > > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > > + > > > > +title: Northwest Logic MIPI-DSI controller on i.MX SoCs > > > > + > > > > +maintainers: > > > > + - Guido G?nther > > > > + - Robert Chiras > > > > + > > > > +description: | > > > > + NWL MIPI-DSI host controller found on i.MX8 platforms. This is a dsi bridge for > > > > + the SOCs NWL MIPI-DSI host controller. > > > > + > > > > +properties: > > > > + compatible: > > > > + const: fsl,imx8mq-nwl-dsi > > > > + > > > > + reg: > > > > + maxItems: 1 > > > > + > > > > + interrupts: > > > > + maxItems: 1 > > > > + > > > > + '#address-cells': > > > > + const: 1 > > > > + > > > > + '#size-cells': > > > > + const: 0 > > > > + > > > > + clocks: > > > > + items: > > > > + - description: DSI core clock > > > > + - description: RX_ESC clock (used in escape mode) > > > > + - description: TX_ESC clock (used in escape mode) > > > > + - description: PHY_REF clock > > > > + - description: LCDIF clock > > > > + > > > > + clock-names: > > > > + items: > > > > + - const: core > > > > + - const: rx_esc > > > > + - const: tx_esc > > > > + - const: phy_ref > > > > + - const: lcdif > > > > + > > > > + mux-controls: > > > > + description: > > > > + mux controller node to use for operating the input mux > > > > + > > > > + phys: > > > > + maxItems: 1 > > > > + description: > > > > + A phandle to the phy module representing the DPHY > > > > + > > > > + phy-names: > > > > + items: > > > > + - const: dphy > > > > + > > > > + power-domains: > > > > + maxItems: 1 > > > > + > > > > + resets: > > > > + items: > > > > + - description: dsi byte reset line > > > > + - description: dsi dpi reset line > > > > + - description: dsi esc reset line > > > > + - description: dsi pclk reset line > > > > + > > > > + reset-names: > > > > + items: > > > > + - const: byte > > > > + - const: dpi > > > > + - const: esc > > > > + - const: pclk > > > > + > > > > + ports: > > > > + type: object > > > > + description: > > > > + A node containing DSI input & output port nodes with endpoint > > > > + definitions as documented in > > > > + Documentation/devicetree/bindings/graph.txt. > > > > + properties: > > > > + port@0: > > > > + type: object > > > > + description: > > > > + Input port node to receive pixel data from the > > > > + display controller. Exactly one endpoint must be > > > > + specified. > > > > + properties: > > > > + '#address-cells': > > > > + const: 1 > > > > + > > > > + '#size-cells': > > > > + const: 0 > > > > + > > > > + endpoint@0: > > > > + description: sub-node describing the input from LCDIF > > > > + type: object > > > > + > > > > + endpoint@1: > > > > + description: sub-node describing the input from DCSS > > > > + type: object > > > > > > This models the two inputs to the IP core, that are connected to a mux > > > internally, controlled through mux-controls, right ? Why is a single > > > endpoint supported then, if there are two connections at the hardware > > > level, and why is this using endpoints instead of ports as there are > > > really two input ports ? > > > > That came out of > > > > https://lore.kernel.org/linux-arm-kernel/c86b7ca2-7799-eafd-c380-e4b551520837@samsung.com/ > > > > # If the ip has separate lines for DCSS and LCDIF you should distinguish > > # by port number. If they are shared > > # you can use endpoint number to specify DCSS or LCDIF, in both cases > > # bindings should be adjusted. > > > > I read that as > > > > - distinguish by endpoint number: > > > > eLCDIF--\ | > > ----| nwl > > DCSS----/ | > > > > - distinguish by port number: > > > > eLCDIF-------| > > | nwl > > DCSS --------| > > I fully agree with you here, but in the first case I would expect the > mux to be outside of the NWL, while in the second case it would be > inside. If I understand the issue correctly, the mux is not part of the > NWL, right ? The endpoint model would then be good, but leaves the issue > Documentation/devicetree/bindings/media/video-mux.txt, but that would > require some support on the driver side. Do you think it would be a good > way forward ? Binding wise that looks like a good fit. I then thought about the implementation and figured we'd end up with something like a bridge that basically muxes inputs - or did you have something different in mind? That sounds generally useful when we e.g. look at runtime switching the input display controller. > The alternative is to consider the mux + NWL as one device (more or less > an i.MX8M-specific integration wrapper of the NWL), but in that case > there should be two ports I believe. I'd go with that for the moment and fold in the above at a later point if needed. I'm happy to work on that but would like to work on some parts of the imx8mq display stack first. Cheers, -- Guido > > From the imx8mq ref manual i didn't see separate input lines for DCSS vs > > eLCDIF the the NWL IP so i went with endpoints instead of ports. I'm > > happy to change that if i got it wrong. > > > > > Apart from that the bindings look ok to me. > > > > > > > + > > > > + reg: > > > > + const: 0 > > > > + > > > > + required: > > > > + - '#address-cells' > > > > + - '#size-cells' > > > > + - reg > > > > + > > > > + oneOf: > > > > + - required: > > > > + - endpoint@0 > > > > + - required: > > > > + - endpoint@1 > > > > + > > > > + additionalProperties: false > > > > + > > > > + port@1: > > > > + type: object > > > > + description: > > > > + DSI output port node to the panel or the next bridge > > > > + in the chain > > > > + > > > > + '#address-cells': > > > > + const: 1 > > > > + > > > > + '#size-cells': > > > > + const: 0 > > > > + > > > > + required: > > > > + - '#address-cells' > > > > + - '#size-cells' > > > > + - port@0 > > > > + - port@1 > > > > + > > > > + additionalProperties: false > > > > + > > > > +patternProperties: > > > > + "^panel@[0-9]+$": > > > > + type: object > > > > + > > > > +required: > > > > + - '#address-cells' > > > > + - '#size-cells' > > > > + - clock-names > > > > + - clocks > > > > + - compatible > > > > + - interrupts > > > > + - mux-controls > > > > + - phy-names > > > > + - phys > > > > + - ports > > > > + - reg > > > > + - reset-names > > > > + - resets > > > > + > > > > +additionalProperties: false > > > > + > > > > +examples: > > > > + - | > > > > + > > > > + #include > > > > + #include > > > > + #include > > > > + > > > > + mipi_dsi: mipi_dsi@30a00000 { > > > > + #address-cells = <1>; > > > > + #size-cells = <0>; > > > > + compatible = "fsl,imx8mq-nwl-dsi"; > > > > + reg = <0x30A00000 0x300>; > > > > + clocks = <&clk IMX8MQ_CLK_DSI_CORE>, > > > > + <&clk IMX8MQ_CLK_DSI_AHB>, > > > > + <&clk IMX8MQ_CLK_DSI_IPG_DIV>, > > > > + <&clk IMX8MQ_CLK_DSI_PHY_REF>, > > > > + <&clk IMX8MQ_CLK_LCDIF_PIXEL>; > > > > + clock-names = "core", "rx_esc", "tx_esc", "phy_ref", "lcdif"; > > > > + interrupts = ; > > > > + mux-controls = <&mux 0>; > > > > + power-domains = <&pgc_mipi>; > > > > + resets = <&src IMX8MQ_RESET_MIPI_DSI_RESET_BYTE_N>, > > > > + <&src IMX8MQ_RESET_MIPI_DSI_DPI_RESET_N>, > > > > + <&src IMX8MQ_RESET_MIPI_DSI_ESC_RESET_N>, > > > > + <&src IMX8MQ_RESET_MIPI_DSI_PCLK_RESET_N>; > > > > + reset-names = "byte", "dpi", "esc", "pclk"; > > > > + phys = <&dphy>; > > > > + phy-names = "dphy"; > > > > + > > > > + panel@0 { > > > > + #address-cells = <1>; > > > > + #size-cells = <0>; > > > > + compatible = "rocktech,jh057n00900"; > > > > + reg = <0>; > > > > + port@0 { > > > > + reg = <0>; > > > > + panel_in: endpoint { > > > > + remote-endpoint = <&mipi_dsi_out>; > > > > + }; > > > > + }; > > > > + }; > > > > + > > > > + ports { > > > > + #address-cells = <1>; > > > > + #size-cells = <0>; > > > > + > > > > + port@0 { > > > > + #size-cells = <0>; > > > > + #address-cells = <1>; > > > > + reg = <0>; > > > > + mipi_dsi_in: endpoint@0 { > > > > + reg = <0>; > > > > + remote-endpoint = <&lcdif_mipi_dsi>; > > > > + }; > > > > + }; > > > > + port@1 { > > > > + reg = <1>; > > > > + mipi_dsi_out: endpoint { > > > > + remote-endpoint = <&panel_in>; > > > > + }; > > > > + }; > > > > + }; > > > > + }; > > -- > Regards, > > Laurent Pinchart >