On Thu, Nov 17, 2022 at 04:14:21PM +0100, Geert Uytterhoeven wrote: > On Thu, Nov 17, 2022 at 1:26 PM Tomi Valkeinen wrote: > > From: Tomi Valkeinen <tomi.valkeinen+renesas@xxxxxxxxxxxxxxxx> > > > > Extend the Renesas DSI display bindings to support the r8a779g0 V4H. > > > > Signed-off-by: Tomi Valkeinen <tomi.valkeinen+renesas@xxxxxxxxxxxxxxxx> > > --- > > .../bindings/display/bridge/renesas,dsi-csi2-tx.yaml | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff --git a/Documentation/devicetree/bindings/display/bridge/renesas,dsi-csi2-tx.yaml b/Documentation/devicetree/bindings/display/bridge/renesas,dsi-csi2-tx.yaml > > index afeeb967393d..bc3101f77e5a 100644 > > --- a/Documentation/devicetree/bindings/display/bridge/renesas,dsi-csi2-tx.yaml > > +++ b/Documentation/devicetree/bindings/display/bridge/renesas,dsi-csi2-tx.yaml > > @@ -11,13 +11,14 @@ maintainers: > > > > description: | > > This binding describes the MIPI DSI/CSI-2 encoder embedded in the Renesas > > - R-Car V3U SoC. The encoder can operate in either DSI or CSI-2 mode, with up > > + R-Car V3U/V4H SoC. The encoder can operate in either DSI or CSI-2 mode, with up > > Perhaps "R-Car Gen4 SoCs", so we stay within 80 chars, and don't have > to update this when the next member of the family is around the block? Sounds good. > Is there anything that might be SoC-specific? > If not, perhaps the time is ripe for a family-specific compatible value? That's hard to tell, I have little visibility into what surprises other SoCs will bring :-S > > to four data lanes. > > > > properties: > > compatible: > > enum: > > - renesas,r8a779a0-dsi-csi2-tx # for V3U > > + - renesas,r8a779g0-dsi-csi2-tx # for V4H Reviewed-by: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > > > > reg: > > maxItems: 1 -- Regards, Laurent Pinchart
