Hi Tomi,
On Thu, Nov 17, 2022 at 1:26 PM Tomi Valkeinen
<tomi.valkeinen@xxxxxxxxxxxxxxxx> 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?
Is there anything that might be SoC-specific?
If not, perhaps the time is ripe for a family-specific compatible value?
> to four data lanes.
>
> properties:
> compatible:
> enum:
> - renesas,r8a779a0-dsi-csi2-tx # for V3U
> + - renesas,r8a779g0-dsi-csi2-tx # for V4H
>
> reg:
> maxItems: 1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
