Hi Laurent,

Thanks for the feedback.

> -----Original Message-----
> From: Laurent Pinchart <laurent.pinch...@ideasonboard.com>
> Sent: Tuesday, April 25, 2023 3:58 AM
> To: Biju Das <biju.das...@bp.renesas.com>
> Cc: David Airlie <airl...@gmail.com>; Daniel Vetter <dan...@ffwll.ch>; Rob
> Herring <robh...@kernel.org>; Krzysztof Kozlowski
> <krzysztof.kozlowski...@linaro.org>; dri-devel@lists.freedesktop.org; linux-
> renesas-...@vger.kernel.org; devicet...@vger.kernel.org; Geert Uytterhoeven
> <geert+rene...@glider.be>; Fabrizio Castro <fabrizio.castro...@renesas.com>;
> Prabhakar Mahadev Lad <prabhakar.mahadev-lad...@bp.renesas.com>; Rob Herring
> <r...@kernel.org>
> Subject: Re: [PATCH v8 2/5] dt-bindings: display: Document Renesas RZ/G2L DU
> bindings
> 
> Hi Biju,
> 
> Thank you for the patch.
> 
> On Mon, Apr 24, 2023 at 05:10:21PM +0100, Biju Das wrote:
> > The RZ/G2L LCD controller is composed of Frame Compression Processor
> > (FCPVD), Video Signal Processor (VSPD), and Display Unit (DU).
> >
> > The DU module supports the following hardware features − Display
> > Parallel Interface (DPI) and MIPI LINK Video Interface − Display
> > timing master − Generates video timings − Selecting the polarity of
> > output DCLK, HSYNC, VSYNC, and DE − Supports Progressive − Input data
> > format (from VSPD): RGB888, RGB666 − Output data format: same as Input
> > data format − Supporting Full HD (1920 pixels x 1080 lines) for
> > MIPI-DSI Output − Supporting WXGA (1280 pixels x 800 lines) for
> > Parallel Output
> >
> > This patch document DU module found on RZ/G2L LCDC.
> >
> > Signed-off-by: Biju Das <biju.das...@bp.renesas.com>
> > Reviewed-by: Rob Herring <r...@kernel.org>
> > ---
> > v7->v8:
> >  * No change
> > v6->v7:
> >  * No change
> > v5->v6:
> >  * No change.
> > v4->v5:
> >  * Added Rb tag from Rob.
> > v3->v4:
> >  * Changed compatible name from
> > renesas,du-r9a07g044->renesas,r9a07g044-du
> >  * started using same compatible for RZ/G2{L,LC}
> > v3: New patch
> > ---
> >  .../bindings/display/renesas,rzg2l-du.yaml    | 124 ++++++++++++++++++
> >  1 file changed, 124 insertions(+)
> >  create mode 100644
> > Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml
> >
> > diff --git
> > a/Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml
> > b/Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml
> > new file mode 100644
> > index 000000000000..ab99e7d57a7d
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml
> > @@ -0,0 +1,124 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2
> > +---
> > +$id:
> > +$schema:
> > +
> > +title: Renesas RZ/G2L Display Unit (DU)
> > +
> > +maintainers:
> > +  - Biju Das <biju.das...@bp.renesas.com>
> > +  - Laurent Pinchart <laurent.pinchart+rene...@ideasonboard.com>
> > +
> > +description: |
> > +  These DT bindings describe the Display Unit embedded in the Renesas
> > +RZ/G2L
> > +  and RZ/V2L SoCs.
> > +
> > +properties:
> > +  compatible:
> > +    enum:
> > +      - renesas,r9a07g044-du # RZ/G2{L,LC}
> > +
> > +  reg:
> > +    maxItems: 1
> > +
> > +  interrupts:
> > +    maxItems: 1
> > +
> > +  clocks:
> > +    items:
> > +      - description: Main clock
> > +      - description: Register access clock
> > +      - description: Video clock
> > +
> > +  clock-names:
> > +    items:
> > +      - const: aclk
> > +      - const: pclk
> > +      - const: vclk
> > +
> > +  resets:
> > +    maxItems: 1
> > +
> > +  power-domains:
> > +    maxItems: 1
> > +
> > +  ports:
> > +    $ref: /schemas/graph.yaml#/properties/ports
> > +    description: |
> > +      The connections to the DU output video ports are modeled using the
> OF
> > +      graph bindings specified in
> Documentation/devicetree/bindings/graph.txt.
> > +      The number of ports and their assignment are model-dependent. Each
> port
> > +      shall have a single endpoint.
> 
> Are there SoCs using this DU that have different ports than the r9a07g044-du
> (and that you can mention publicly :-)) ? If not, I'd drop "The number of
> ports ... model-dependent", and list the ports
> explicitly:


Yes, RZ/G2UL SoC(r9a07g043-du) supports only parallel interface.

RZ/{G2L, V2L} DU is similar to R-Car V3M, on V3M, "Display Unit is a module to 
input an image data from VSP and to output the data to LVDS-IF,and digital RGB 
etc. in accordance with optionally settable display timing."

In RZ/{G2L, V2L} case, DU is a module to input an image data from VSP and to 
output the data to DSI and digital RGB.
− Supporting Full HD (1920 pixels × 1080 lines) for MIPI-DSI Output
− Supporting WXGA (1280 pixels × 800 lines) for Parallel Output

RZ/G2L and RG/G2LC are almost identical SoCs, but RZ/G2LC support only DSI 
interface.

> 
>     properties:
>       port@0:
>         $ref: /schemas/graph.yaml#/properties/port
>       description: DSI output port
>         unevaluatedProperties: false
> 
>       port@1:
>         $ref: /schemas/graph.yaml#/properties/port
>       description: DPI output port
>         unevaluatedProperties: false
> 
> The alternative is to specify this in compatible-specific schema rules like
> in renesas,du.yaml, which is more complicated.

> 
> I'm also wondering, are there really two output ports ? Or does the DU have
> a single output, whose signals are output on the parallel interface and also
> connected to the DSI encoder ?

It is similar to RCar V3M right? On V3M case, image data from VSP is output to 
(LVDS and RGB) and here it is (DSI and RGB)??

Cheers,
Biju

> 
> > +
> > +    patternProperties:
> > +      "^port@[0-1]$":
> > +        $ref: /schemas/graph.yaml#/properties/port
> > +        unevaluatedProperties: false
> > +
> > +    required:
> > +      - port@0
> > +
> > +    unevaluatedProperties: false
> > +
> > +  renesas,vsps:
> > +    $ref: "/schemas/types.yaml#/definitions/phandle-array"
> > +    items:
> > +      items:
> > +        - description: phandle to VSP instance that serves the DU channel
> > +        - description: Channel index identifying the LIF instance in that
> VSP
> > +    description:
> > +      A list of phandle and channel index tuples to the VSPs that handle
> the
> > +      memory interfaces for the DU channels.
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +  - interrupts
> > +  - clocks
> > +  - clock-names
> > +  - resets
> > +  - power-domains
> > +  - ports
> > +  - renesas,vsps
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > +  # RZ/G2L DU
> > +  - |
> > +    #include <dt-bindings/clock/r9a07g044-cpg.h>
> > +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> > +
> > +    display@10890000 {
> > +        compatible = "renesas,r9a07g044-du";
> > +        reg = <0x10890000 0x10000>;
> > +        interrupts = <GIC_SPI 152 IRQ_TYPE_LEVEL_HIGH>;
> > +        clocks = <&cpg CPG_MOD R9A07G044_LCDC_CLK_A>,
> > +                 <&cpg CPG_MOD R9A07G044_LCDC_CLK_P>,
> > +                 <&cpg CPG_MOD R9A07G044_LCDC_CLK_D>;
> > +        clock-names = "aclk", "pclk", "vclk";
> > +        resets = <&cpg R9A07G044_LCDC_RESET_N>;
> > +        power-domains = <&cpg>;
> > +
> > +        renesas,vsps = <&vspd0 0>;
> > +
> > +        ports {
> > +            #address-cells = <1>;
> > +            #size-cells = <0>;
> > +
> > +            port@0 {
> > +                reg = <0>;
> > +                endpoint {
> > +                    remote-endpoint = <&dsi0_in>;
> > +                };
> > +            };
> > +            port@1 {
> > +                reg = <1>;
> > +                endpoint {
> > +                };
> > +            };
> > +        };
> > +    };
> > +
> > +...
> 
> --
> Regards,
> 
> Laurent Pinchart

Reply via email to