Re: [PATCH v2 2/5] dt-bindings: display: bridge: Document Renesas R-Car V4H DSC bindings

[Laurent Pinchart]

On Fri, Jun 12, 2026 at 05:09:48PM +0100, Conor Dooley wrote:
> On Fri, Jun 12, 2026 at 01:43:44PM +0300, Tomi Valkeinen wrote:
> > On 15/05/2026 20:32, Conor Dooley wrote:
> > > On Fri, May 15, 2026 at 10:56:15AM +0300, Tomi Valkeinen wrote:
> > > > From: Marek Vasut <marek.vasut+renesas@xxxxxxxxxxx>
> > > > 
> > > > The Renesas DSC Display Stream Compression is a bridge embedded in the
> > > > Renesas R-Car V4H SoC. The bridge performs VESA DSC encoding of up to
> > > > 8k or 400 Mpixel/s .
> > > > 
> > > > Signed-off-by: Marek Vasut <marek.vasut+renesas@xxxxxxxxxxx>
> > > > [tomi.valkeinen: fix the example]
> > > > Signed-off-by: Tomi Valkeinen <tomi.valkeinen+renesas@xxxxxxxxxxxxxxxx>
> > > > ---
> > > >   .../bindings/display/bridge/renesas,dsc.yaml       | 96 ++++++++++++++++++++++
> > > >   1 file changed, 96 insertions(+)
> > > > 
> > > > diff --git a/Documentation/devicetree/bindings/display/bridge/renesas,dsc.yaml b/Documentation/devicetree/bindings/display/bridge/renesas,dsc.yaml
> > > > new file mode 100644
> > > > index 000000000000..2918d592732b
> > > > --- /dev/null
> > > > +++ b/Documentation/devicetree/bindings/display/bridge/renesas,dsc.yaml
> > > 
> > > Filename matching the compatible please.
> > 
> > All the other Documentation/devicetree/bindings/display/bridge/renesas,*
> > files follow the same style, where the file name is in a generic format, but
> > the actual compat strings are per SoC (and no generic compat string).
> 
> No idea why it's like that currently, but filename matching compatible
> is the policy.

I wonder if we should use

  compatible:
    items:
      - enum:
          - renesas,r8a779g0-dsc
      - const: renesas,rcar-dsc

to prepare for the other SoCs that include a DSC. It's of course hard to
predict how compatible all new silicon will be, but we know there will
be some compatible ones.

This being said, looking for instance at renesas,du.yaml in the same
directory, we have

  compatible:
    enum:
      - renesas,du-r8a7742 # for RZ/G1H compatible DU
      - renesas,du-r8a7743 # for RZ/G1M compatible DU
      - renesas,du-r8a7744 # for RZ/G1N compatible DU
      - renesas,du-r8a7745 # for RZ/G1E compatible DU
      - renesas,du-r8a77470 # for RZ/G1C compatible DU
      - renesas,du-r8a774a1 # for RZ/G2M compatible DU
      - renesas,du-r8a774b1 # for RZ/G2N compatible DU
      - renesas,du-r8a774c0 # for RZ/G2E compatible DU
      - renesas,du-r8a774e1 # for RZ/G2H compatible DU
      - renesas,du-r8a7779 # for R-Car H1 compatible DU
      - renesas,du-r8a7790 # for R-Car H2 compatible DU
      - renesas,du-r8a7791 # for R-Car M2-W compatible DU
      - renesas,du-r8a7792 # for R-Car V2H compatible DU
      - renesas,du-r8a7793 # for R-Car M2-N compatible DU
      - renesas,du-r8a7794 # for R-Car E2 compatible DU
      - renesas,du-r8a7795 # for R-Car H3 compatible DU
      - renesas,du-r8a7796 # for R-Car M3-W compatible DU
      - renesas,du-r8a77961 # for R-Car M3-W+ compatible DU
      - renesas,du-r8a77965 # for R-Car M3-N compatible DU
      - renesas,du-r8a77970 # for R-Car V3M compatible DU
      - renesas,du-r8a77980 # for R-Car V3H compatible DU
      - renesas,du-r8a77990 # for R-Car E3 compatible DU
      - renesas,du-r8a77995 # for R-Car D3 compatible DU
      - renesas,du-r8a779a0 # for R-Car V3U compatible DU
      - renesas,du-r8a779g0 # for R-Car V4H compatible DU
      - renesas,du-r8a779h0 # for R-Car V4M compatible DU

Could the file have been named renesas,du-r8a7790.yaml ? Sure. Would it
be better for users than renesas,du.yaml ? I'm less sure.

-- 
Regards,

Laurent Pinchart