devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Scally <dan.scally@ideasonboard.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	jacopo.mondi@ideasonboard.com, biju.das.jz@bp.renesas.com
Subject: Re: [PATCH v2 1/3] dt-bindings: media: Add bindings for the RZ/V2H IVC block
Date: Tue, 24 Jun 2025 15:16:07 +0200	[thread overview]
Message-ID: <cfc25ba6-753e-41bd-8cb6-f31ba57593a8@kernel.org> (raw)
In-Reply-To: <20250624-ivc-v2-1-e4ecdddb0a96@ideasonboard.com>

On 24/06/2025 14:35, Daniel Scally wrote:
> The RZ/V2H SoC has a block called the Input Video Control block which
> feeds image data into the Image Signal Processor. Add dt bindings to
> describe the IVC.
> 
> Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>
> ---
> Changes in v2:
> 
> 	- compatible matches filename

This is not what I asked.

> 	- Added power-domains
> 	- Aligned clock and reset entries on opening "<"
> 	- Removed status = "okay"; from example
> ---
>  .../bindings/media/renesas,rzv2h-ivc.yaml          | 103 +++++++++++++++++++++
>  1 file changed, 103 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/media/renesas,rzv2h-ivc.yaml b/Documentation/devicetree/bindings/media/renesas,rzv2h-ivc.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..ee0849eeeaba840cf43c81d69449c631ad1c6a6a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/renesas,rzv2h-ivc.yaml
> @@ -0,0 +1,103 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/renesas,rzv2h-ivc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Renesas RZ/V2H Input Video Control Block
> +
> +maintainers:
> +  - Daniel Scally <dan.scally@ideasonboard.com>
> +
> +description:
> +  The IVC block is a module that takes video frames from memory and feeds them
> +  to the Image Signal Processor for processing.
> +
> +properties:
> +  compatible:
> +    const: renesas,rzv2h-ivc

No, you cannot use generic compatibles. See writing bindings (or
basically every review from DT maintainers).

> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +
> +  clocks:
> +    items:
> +      - description: Input Video Control block register access clock
> +      - description: Video input data AXI bus clock
> +      - description: ISP system clock
> +
> +  clock-names:
> +    items:
> +      - const: pclk
> +      - const: vin_aclk

aclk

vin is redundant. This cannot be anything else than vin.

> +      - const: sclk
> +
> +  power-domains:
> +    maxItems: 1
> +
> +  resets:
> +    items:
> +      - description: Input Video Control block register access reset
> +      - description: Video input data AXI bus reset
> +      - description: ISP core reset
> +
> +  reset-names:
> +    items:
> +      - const: presetn
> +      - const: vin_aresetn
> +      - const: sresetn


s/reset// because it is redundant... which would point to pretty
pointless names. Look at your description - one is core or registers,
second is vin and other is isp-core... although then I wonder why ISP
input resets ISP core?



Best regards,
Krzysztof

  reply	other threads:[~2025-06-24 13:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 12:35 [PATCH v2 0/3] Add Input Video Control Block driver for RZ/V2H Daniel Scally
2025-06-24 12:35 ` [PATCH v2 1/3] dt-bindings: media: Add bindings for the RZ/V2H IVC block Daniel Scally
2025-06-24 13:16   ` Krzysztof Kozlowski [this message]
2025-06-24 14:17     ` Dan Scally
2025-06-24 15:41       ` Krzysztof Kozlowski
2025-06-24 16:45       ` Geert Uytterhoeven
2025-06-24 17:50         ` Dan Scally
2025-06-24 12:35 ` [PATCH v2 2/3] media: platform: Add Renesas Input Video Control block driver Daniel Scally
2025-06-30 16:05   ` Jacopo Mondi
2025-06-30 21:32     ` Dan Scally
2025-07-01 11:10       ` Jacopo Mondi
2025-07-01 11:27         ` Dan Scally
2025-07-01 12:58           ` Jacopo Mondi
2025-07-01 13:01             ` Dan Scally
2025-07-01 13:17               ` Jacopo Mondi
2025-07-01 13:21                 ` Dan Scally
2025-07-01 13:31                   ` Jacopo Mondi
2025-07-01 13:33                     ` Dan Scally
2025-07-01  8:34   ` Philipp Zabel
2025-07-01 13:24     ` Dan Scally
2025-06-24 12:36 ` [PATCH v2 3/3] MAINTAINERS: Add entry for rzv2h-ivc driver Daniel Scally
2025-06-24 12:52 ` [PATCH v2 0/3] Add Input Video Control Block driver for RZ/V2H Krzysztof Kozlowski
2025-06-24 13:10   ` Dan Scally

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=cfc25ba6-753e-41bd-8cb6-f31ba57593a8@kernel.org \
    --to=krzk@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=conor+dt@kernel.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --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).