From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Conor Dooley <conor@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: media: renesas,vin: Add binding for V4M
Date: Thu, 20 Jun 2024 19:22:37 +0200 [thread overview]
Message-ID: <20240620172237.GA3623951@ragnatech.se> (raw)
In-Reply-To: <20240620-gating-coherent-af984389b2d7@spud>
On 2024-06-20 17:27:00 +0100, Conor Dooley wrote:
> > + - items:
> > + - enum:
> > - renesas,vin-r8a779g0 # R-Car V4H
> > + - renesas,vin-r8a779h0 # R-Car V4M
> > + - const: renesas,rcar-gen4-vin # Generic R-Car Gen4
> >
> > If so I can see that working as I could still fix any issues that come
> > from differences between V4H and V4M if needed. If so do you think it
> > best to add this in two different patches? One to add the
> > renesas,rcar-gen4-vin fallback (which will also need DTS updates to fix
> > warnings from exciting users of V4H not listing the gen4 fallback) and
> > one to add V4M?
>
>
> I would just do:
> diff --git a/Documentation/devicetree/bindings/media/renesas,vin.yaml b/Documentation/devicetree/bindings/media/renesas,vin.yaml
> index 5539d0f8e74d..22bbad42fc03 100644
> --- a/Documentation/devicetree/bindings/media/renesas,vin.yaml
> +++ b/Documentation/devicetree/bindings/media/renesas,vin.yaml
> @@ -54,6 +54,9 @@ properties:
> - renesas,vin-r8a77995 # R-Car D3
> - renesas,vin-r8a779a0 # R-Car V3U
> - renesas,vin-r8a779g0 # R-Car V4H
> + - items:
> + - const: renesas,vin-r8a779h0 # R-Car V4L2
> + - const: renesas,vin-r8a779g0 # R-Car V4H
@Geert: What do you think about this? This would be a first use-case for
compatibles crossing SoC DTS files that I know of. I'm a bit uneasy
going down this road.
Would this not also effect the existing users of renesas,vin-r8a779g0
which would now need something similar to what you propose below with a
list of SoC compatibles and a fallback.
>
> reg:
> maxItems: 1
>
> Which requires no driver or dts changes. That could become:
> - items:
> - enum:
> - renesas,vin-r8a779h0 # R-Car V4L2
> - renesas,vin-r8a779i0 # R-Car R4P17
> - const: renesas,vin-r8a779g0 # R-Car V4H
FWIW, on Gen2 where fallback es where useful compared to Gen3 we did
this with "renesas,rcar-gen2-vin".
>
> if there's another compatible device in the future.
>
> > Apologies again for the confusion.
>
> dw about it
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2024-06-20 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:35 [PATCH v3 0/2] rcar-vin: Add support for R-Car V4M Niklas Söderlund
2024-06-19 15:35 ` [PATCH v3 1/2] dt-bindings: media: renesas,vin: Add binding for V4M Niklas Söderlund
2024-06-19 17:33 ` Conor Dooley
2024-06-19 18:56 ` Niklas Söderlund
2024-06-19 20:43 ` Niklas Söderlund
2024-06-20 16:27 ` Conor Dooley
2024-06-20 17:22 ` Niklas Söderlund [this message]
2024-06-21 7:21 ` Geert Uytterhoeven
2024-06-24 9:20 ` Niklas Söderlund
2024-06-24 10:36 ` Conor Dooley
2024-06-24 12:50 ` Niklas Söderlund
2024-06-24 13:17 ` Conor Dooley
2024-06-19 15:35 ` [PATCH v3 2/2] media: rcar-vin: Add support for R-Car V4M Niklas Söderlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240620172237.GA3623951@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).