From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6A24E281525; Thu, 9 Apr 2026 13:24:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.167.242.64 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775741065; cv=none; b=lliahGzHPTFg4fQwSv6ojB3ZtOlrq218bnppY64BUaaxd9U5yEw2CLOnbNi9QbF6rdhTrusPER+Cpo3Il9vdLdUyFS30I4RNI2/ergt9eCypfFEZg/UwShjBksryflPzm8vDQ/X+8X+8jmP3JiwARrKM73y5nOcboH7sJvQ1VIg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775741065; c=relaxed/simple; bh=Ovv1KhJxsyv9ZiasmUoDMdpsxH9MTww+Hbj6QUK4fMk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=XFPKPHiA2MTBGB4XaqGwQGufZtCCpDQ+twAvXg1bxl4fGc0eWLoWT0u441bC6NCcEopQFblIJNBRip+KPKtem6/H8OYfz3HPehbsH1qRgt99RPn5usX4hhJ5IpBlyZyoKt/Yfhwn8Dszy5BKrU2oLWpJEKL+MqGMtwrGBt1VxJQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com; spf=pass smtp.mailfrom=ideasonboard.com; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b=UY4lszcA; arc=none smtp.client-ip=213.167.242.64 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="UY4lszcA" Received: from killaraus.ideasonboard.com (2001-14ba-703d-e500--2a1.rev.dnainternet.fi [IPv6:2001:14ba:703d:e500::2a1]) by perceval.ideasonboard.com (Postfix) with UTF8SMTPSA id E65901123; Thu, 9 Apr 2026 15:22:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1775740973; bh=Ovv1KhJxsyv9ZiasmUoDMdpsxH9MTww+Hbj6QUK4fMk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UY4lszcAeDes9R4oFWxCOAmpPdSTmMXa9+XcqGXo+0wdJmcx2z+ltKVkGCrMSu5q4 OL5ZV42G01KOzC3dr1uciLVs0LUDrq9hEMORgdCb12bEaT9P6SyS1hcLlr2PCkvYsZ ZIZ02mNiWwWwSlJQgLcTFexgGjPzseBb32BIevfo= Date: Thu, 9 Apr 2026 16:24:20 +0300 From: Laurent Pinchart To: Tommaso Merciai Cc: tomm.merciai@gmail.com, geert@linux-m68k.org, linux-renesas-soc@vger.kernel.org, biju.das.jz@bp.renesas.com, Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Geert Uytterhoeven , Michael Turquette , Stephen Boyd , Magnus Damm , Tomi Valkeinen , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org Subject: Re: [PATCH v6 10/21] dt-bindings: display: renesas,rzg2l-du: Add support for RZ/G3E SoC Message-ID: <20260409132420.GD2634584@killaraus.ideasonboard.com> References: <8f814f22ff62dcde6153260e2c8c29a5415c9a89.1775636898.git.tommaso.merciai.xr@bp.renesas.com> <20260408122436.GH1928916@killaraus.ideasonboard.com> <20260408141638.GA1965119@killaraus.ideasonboard.com> <87a18664-d19e-4434-8f92-1c7ce4f3a131@bp.renesas.com> <20260408150053.GC1965119@killaraus.ideasonboard.com> <61f294e8-f9ae-4868-8dba-60250279ef21@bp.renesas.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <61f294e8-f9ae-4868-8dba-60250279ef21@bp.renesas.com> On Thu, Apr 09, 2026 at 01:15:18PM +0200, Tommaso Merciai wrote: > On 4/8/26 17:00, Laurent Pinchart wrote: > > On Wed, Apr 08, 2026 at 04:44:48PM +0200, Tommaso Merciai wrote: > >> On 4/8/26 16:16, Laurent Pinchart wrote: > >>> On Wed, Apr 08, 2026 at 04:02:14PM +0200, Tommaso Merciai wrote: > >>>> On 4/8/26 14:24, Laurent Pinchart wrote: > >>>>> On Wed, Apr 08, 2026 at 12:36:55PM +0200, Tommaso Merciai wrote: > >>>>>> The RZ/G3E SoC has 2 LCD controllers (LCDC), each containing a Frame > >>>>>> Compression Processor (FCPVD), a Video Signal Processor (VSPD), and a > >>>>>> Display Unit (DU). > >>>>>> > >>>>>> - LCDC0 supports DSI and LVDS (single or dual-channel) outputs. > >>>>>> - LCDC1 supports DSI, LVDS (single-channel), and RGB outputs. > >>>>>> > >>>>>> Add a new SoC-specific compatible string 'renesas,r9a09g047-du'. > >>>>>> > >>>>>> Extend patternProperties from "^port@[0-1]$" to "^port@[0-3]$" to > >>>>>> allow up to four output ports, and explicitly disable port@2 and port@3 > >>>>>> for existing SoCs that do not expose them. > >>>>>> > >>>>>> Describe the four output ports of the RZ/G3E DU: > >>>>>> > >>>>>> - port@0: DSI (available on both LCDC instances) > >>>>>> - port@1: DPAD / parallel RGB (LCDC1 only) > >>>>>> - port@2: LVDS channel 0 (LCDC0 only) > >>>>>> - port@3: LVDS channel 1 (available on both LCDC instances) > >>>>>> > >>>>>> Signed-off-by: Tommaso Merciai > >>>>>> --- > >>>>>> v5->v6: > >>>>>> - Extend patternProperties from "^port@[0-1]$" to "^port@[0-3]$" and > >>>>>> explicitly disable port@2 and port@3 for existing SoCs that do not expose > >>>>>> them. > >>>>>> - Reworked ports numbering + improved/fixed ports descriptions in the > >>>>>> bindings documentation. > >>>>>> - Improved commit body. > >>>>>> > >>>>>> v4->v5: > >>>>>> - Dropped renesas,id property and updated bindings > >>>>>> accordingly. > >>>>>> > >>>>>> v2->v3: > >>>>>> - No changes. > >>>>>> > >>>>>> v2->v3: > >>>>>> - No changes. > >>>>>> > >>>>>> v1->v2: > >>>>>> - Use single compatible string instead of multiple compatible strings > >>>>>> for the two DU instances, leveraging a 'renesas,id' property to > >>>>>> differentiate between DU0 and DU1. > >>>>>> - Updated commit message accordingly. > >>>>>> > >>>>>> .../bindings/display/renesas,rzg2l-du.yaml | 30 ++++++++++++++++++- > >>>>>> 1 file changed, 29 insertions(+), 1 deletion(-) > >>>>>> > >>>>>> diff --git a/Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml b/Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml > >>>>>> index 5add3b832eab..32da0b5ec88c 100644 > >>>>>> --- a/Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml > >>>>>> +++ b/Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml > >>>>>> @@ -20,6 +20,7 @@ properties: > >>>>>> - enum: > >>>>>> - renesas,r9a07g043u-du # RZ/G2UL > >>>>>> - renesas,r9a07g044-du # RZ/G2{L,LC} > >>>>>> + - renesas,r9a09g047-du # RZ/G3E > >>>>>> - renesas,r9a09g057-du # RZ/V2H(P) > >>>>>> - items: > >>>>>> - enum: > >>>>>> @@ -61,7 +62,7 @@ properties: > >>>>>> model-dependent. Each port shall have a single endpoint. > >>>>>> > >>>>>> patternProperties: > >>>>>> - "^port@[0-1]$": > >>>>>> + "^port@[0-3]$": > >>>>>> $ref: /schemas/graph.yaml#/properties/port > >>>>>> unevaluatedProperties: false > >>>>>> > >>>>>> @@ -103,6 +104,8 @@ allOf: > >>>>>> port@0: > >>>>>> description: DPI > >>>>>> port@1: false > >>>>>> + port@2: false > >>>>>> + port@3: false > >>>>>> > >>>>>> required: > >>>>>> - port@0 > >>>>>> @@ -119,6 +122,8 @@ allOf: > >>>>>> description: DSI > >>>>>> port@1: > >>>>>> description: DPI > >>>>>> + port@2: false > >>>>>> + port@3: false > >>>>>> > >>>>>> required: > >>>>>> - port@0 > >>>>>> @@ -135,9 +140,32 @@ allOf: > >>>>>> port@0: > >>>>>> description: DSI > >>>>>> port@1: false > >>>>>> + port@2: false > >>>>>> + port@3: false > >>>>>> > >>>>>> required: > >>>>>> - port@0 > >>>>>> + - if: > >>>>>> + properties: > >>>>>> + compatible: > >>>>>> + contains: > >>>>>> + const: renesas,r9a09g047-du > >>>>>> + then: > >>>>>> + properties: > >>>>>> + ports: > >>>>>> + properties: > >>>>>> + port@0: > >>>>>> + description: DSI > >>>>>> + port@1: > >>>>>> + description: DPAD > >>>>>> + port@2: > >>>>>> + description: LVDS, Channel 0 > >>>>>> + port@3: > >>>>>> + description: LVDS, Channel 1 > >>>>>> + > >>>>>> + required: > >>>>>> + - port@0 > >>>>>> + - port@3 > >>>>> > >>>>> Why are ports 1 and 2 not required ? > >>>> > >>>> About this we had a similar discussion on v5[0] > >>>> We are using the same compatible and: > >>>> > >>>> - LCDC0 supports DSI and LVDS (single or dual-channel) outputs. > >>>> | > >>>> --> then has: > >>>> port@0 > >>>> port@2 > >>>> port@3 > >>>> > >>>> > >>>> - LCDC1 supports DSI, LVDS (single-channel), and RGB outputs. > >>>> | > >>>> --> then has: > >>>> port@0 > >>>> port@1 > >>>> port@3 > >>> > >>> Ah yes, I forget there are two LCDC instances with different output > >>> configurations. > >>> > >>> Something still looks a bit weird to me though. For LCDC1, which > >>> supports a single LVDS channel, you use the port described as the second > >>> LVDS channel. Is there a reason not to use port@2 ? > >> > >> 9.11 Low Voltage Differential Signaling (LVDS) > >> 9.11.1.2 Block Diagram > >> Figure 9.11-1 shows a block diagram of LVDS. > >> > >> LCDC1 is connected to LVDS, Channel 1 > >> For this reason I'm using port@3. > > > > Re-reading that, I think I've misinterpreted the hardware architecture. > > Doesn't the DU have a single output, that is connected the multiple > > encoders (LVDS and DSI for LCDC0 and LVDS, DSI and DPI for LCDC1) ? It > > seems modelling it with a single port and multiple endpoints would > > better match the device. > > > > For LVDS in particular, I see a single LVDS encoder with two channels, > > so there should not be two LVDS output ports in the DU. The two ports > > should be on the output of the LVDS device. > > You are suggesting the following dt architecture: > > du0: display@16460000 { > compatible = "renesas,r9a09g047-du"; > reg = <0 0x16460000 0 0x10000>; > interrupts = ; > clocks = <&cpg CPG_MOD 0xed>, > <&cpg CPG_MOD 0xee>, > <&cpg CPG_MOD 0xef>; > clock-names = "aclk", "pclk", "vclk"; > power-domains = <&cpg>; > resets = <&cpg 0xdc>; > renesas,vsps = <&vspd0 0>; > status = "disabled"; > > port { > du0_out_dsi: endpoint@0 { > reg = <0>; > }; > > du0_out_lvds0: endpoint@2 { > reg = <2>; > }; > > du0_out_lvds1: endpoint@3 { > reg = <3>; > }; > } > }; > > du1: display@16490000 { > compatible = "renesas,r9a09g047-du"; > reg = <0 0x16490000 0 0x10000>; > interrupts = ; > clocks = <&cpg CPG_MOD 0x1a8>, > <&cpg CPG_MOD 0x1a9>, > <&cpg CPG_MOD 0x1aa>; > clock-names = "aclk", "pclk", "vclk"; > power-domains = <&cpg>; > resets = <&cpg 0x11e>; > renesas,vsps = <&vspd1 0>; > status = "disabled"; > > port { > du1_out_dsi: endpoint@0 { > reg = <0>; > }; > > du1_out_rgb: endpoint@1 { > reg = <1>; > }; > > du1_out_lvds1: endpoint@3 { > reg = <3>; > }; > } > }; > > > Please correct me if I'm wrong. That's right. It would match the hardware, or at least my understanding of the hardware based on the documentation. As far as I can tell, each DU has a single 24-bit output port connected to multiple encoders. > >>>> Then port@1 is required for DU1 but not for DU0. > >>>> Same port@2 is required for DU0 but not for DU1. > >>>> > >>>> [0] https://patchwork.kernel.org/project/linux-renesas-soc/patch/ca022fdbba5236c36e0cb3095db4c31e8e0cb1b8.1770996493.git.tommaso.merciai.xr@bp.renesas.com/ > >>>> > >>>>>> > >>>>>> examples: > >>>>>> # RZ/G2L DU -- Regards, Laurent Pinchart