From: Conor Dooley <conor@kernel.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
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 v4 4/5] dt-bindings: media: renesas,vin: Add binding for V4M
Date: Wed, 26 Jun 2024 12:39:25 +0100 [thread overview]
Message-ID: <20240626-enforced-flock-965380c1c1f0@spud> (raw)
In-Reply-To: <20240624144108.1771189-5-niklas.soderlund+renesas@ragnatech.se>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Mon, Jun 24, 2024 at 04:41:07PM +0200, Niklas Söderlund wrote:
> Document support for the VIN module in the Renesas V4M (r8a779h0) SoC.
> This device is compatible with the VIN module on the other Gen4 SoC,
> V4H.
Provided a family compatible like this actually makes sense, and is not
just being done to appease my want of a fallback:
Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> * Changes since v3
> - State in commit message that device is compatible with the other Gen4
> device.
> ---
> Documentation/devicetree/bindings/media/renesas,vin.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/media/renesas,vin.yaml b/Documentation/devicetree/bindings/media/renesas,vin.yaml
> index c3ef4fde7baf..ec8a8d87dc24 100644
> --- a/Documentation/devicetree/bindings/media/renesas,vin.yaml
> +++ b/Documentation/devicetree/bindings/media/renesas,vin.yaml
> @@ -56,6 +56,7 @@ properties:
> - items:
> - enum:
> - renesas,vin-r8a779g0 # R-Car V4H
> + - renesas,vin-r8a779h0 # R-Car V4M
> - const: renesas,rcar-gen4-vin # Generic R-Car Gen4
>
> reg:
> --
> 2.45.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-26 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 14:41 [PATCH v4 0/5] rcar-vin: Add support for R-Car V4M Niklas Söderlund
2024-06-24 14:41 ` [PATCH v4 1/5] dt-bindings: media: renesas,vin: Add Gen4 family fallback Niklas Söderlund
2024-06-26 11:44 ` Conor Dooley
2024-07-02 7:52 ` Geert Uytterhoeven
2024-07-02 9:06 ` Niklas Söderlund
2024-06-24 14:41 ` [PATCH v4 2/5] arm64: dts: renesas: r8a779g0: Add family fallback for VIN IP Niklas Söderlund
2024-07-02 7:52 ` Geert Uytterhoeven
2024-06-24 14:41 ` [PATCH v4 3/5] media: rcar-vin: Add family compatible for R-Car Gen4 family Niklas Söderlund
2024-07-02 7:57 ` Geert Uytterhoeven
2024-06-24 14:41 ` [PATCH v4 4/5] dt-bindings: media: renesas,vin: Add binding for V4M Niklas Söderlund
2024-06-26 11:39 ` Conor Dooley [this message]
2024-07-02 7:58 ` Geert Uytterhoeven
2024-06-24 14:41 ` [PATCH v4 5/5] arm64: dts: renesas: r8a779h0: Add family fallback for VIN IP Niklas Söderlund
2024-07-02 7:58 ` Geert Uytterhoeven
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=20240626-enforced-flock-965380c1c1f0@spud \
--to=conor@kernel.org \
--cc=conor+dt@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=niklas.soderlund+renesas@ragnatech.se \
--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).