From: Biju Das <biju.das.jz@bp.renesas.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
biju.das.au <biju.das.au@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: RE: [PATCH v3 2/2] media: dt-bindings: renesas,rzg2l-cru: Document Renesas RZ/G2UL CRU block
Date: Thu, 2 May 2024 10:51:22 +0000 [thread overview]
Message-ID: <TYCPR01MB113324049EB71B18E63A075DF86182@TYCPR01MB11332.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20240213142941.161217-3-biju.das.jz@bp.renesas.com>
Hi All,
Gentle ping. Looks like it missed out in previous kernel cycle.
Are we happy with this patch?
Cheers,
Biju
> -----Original Message-----
> From: Biju Das <biju.das.jz@bp.renesas.com>
> Sent: Tuesday, February 13, 2024 2:30 PM
> Subject: [PATCH v3 2/2] media: dt-bindings: renesas,rzg2l-cru: Document Renesas RZ/G2UL CRU block
>
> Document the CRU IP found in Renesas RZ/G2UL SoC.
>
> The CRU block on the RZ/G2UL SoC is identical to one found on the RZ/G2L SoC, but it does not
> support parallel input.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v2->v3:
> * Added Ack from Conor Dooley and Rb tag from Geert.
> v1->v2:
> * Dropped the description from if/else block.
> * Dropped driver reference from commit description.
> ---
> .../bindings/media/renesas,rzg2l-cru.yaml | 35 ++++++++++++++++---
> 1 file changed, 31 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/renesas,rzg2l-cru.yaml
> b/Documentation/devicetree/bindings/media/renesas,rzg2l-cru.yaml
> index 1e72b8808d24..bc1245127025 100644
> --- a/Documentation/devicetree/bindings/media/renesas,rzg2l-cru.yaml
> +++ b/Documentation/devicetree/bindings/media/renesas,rzg2l-cru.yaml
> @@ -19,6 +19,7 @@ properties:
> compatible:
> items:
> - enum:
> + - renesas,r9a07g043-cru # RZ/G2UL
> - renesas,r9a07g044-cru # RZ/G2{L,LC}
> - renesas,r9a07g054-cru # RZ/V2L
> - const: renesas,rzg2l-cru
> @@ -87,10 +88,6 @@ properties:
> Input port node, describing the Image Processing module connected to the
> CSI-2 receiver.
>
> - required:
> - - port@0
> - - port@1
> -
> required:
> - compatible
> - reg
> @@ -102,6 +99,36 @@ required:
> - reset-names
> - power-domains
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - renesas,r9a07g044-cru
> + - renesas,r9a07g054-cru
> + then:
> + properties:
> + ports:
> + required:
> + - port@0
> + - port@1
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - renesas,r9a07g043-cru
> + then:
> + properties:
> + ports:
> + properties:
> + port@0: false
> +
> + required:
> + - port@1
> +
> additionalProperties: false
>
> examples:
> --
> 2.25.1
next prev parent reply other threads:[~2024-05-02 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 14:29 [PATCH v3 0/2] Document RZ/G2UL CRU and CSI support Biju Das
2024-02-13 14:29 ` [PATCH v3 1/2] media: dt-bindings: renesas,rzg2l-csi2: Document Renesas RZ/G2UL CSI-2 block Biju Das
2024-05-02 10:49 ` Biju Das
2024-02-13 14:29 ` [PATCH v3 2/2] media: dt-bindings: renesas,rzg2l-cru: Document Renesas RZ/G2UL CRU block Biju Das
2024-05-02 10:51 ` Biju Das [this message]
2024-03-13 10:39 ` [PATCH v3 0/2] Document RZ/G2UL CRU and CSI support Biju Das
2024-05-01 6:32 ` Biju Das
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=TYCPR01MB113324049EB71B18E63A075DF86182@TYCPR01MB11332.jpnprd01.prod.outlook.com \
--to=biju.das.jz@bp.renesas.com \
--cc=biju.das.au@gmail.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mchehab@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).