Linux Media Controller development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dan 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 17:41:26 +0200	[thread overview]
Message-ID: <83755309-230f-4a5d-a658-f5f0d8714e9a@kernel.org> (raw)
In-Reply-To: <c2ab887c-398d-49c4-9ae6-1d0986c32781@ideasonboard.com>

On 24/06/2025 16:17, Dan Scally wrote:
> 
> OK...to throw a spanner into this, I think there's actually two soc codes with the IP; r9a09g057h44 
> and r9a09g057h48. renesas,rzg2l-cru.yaml and renesas,rzg2l-csi2.yaml seem to use the 'generic' code 
> in a way that suggests this:
> 
> compatible:
>          items:
>              - enum:
>                  - renesas,r9a09g057h44-ivc
>                  - renesas,r9a09g057h48-ivc
>              - const: renesas,rzv2h-ivc

There were several reviews where we or at lest me disagreed with above
and explained, with arguments, that this is less welcomed choice.

> 
> 
> And then the filename stays as it is, but the example-schema.yaml to me suggests this, without the 
> 'generic' code there at all:
> 
> 
> compatible:
>          items:
>              - enum:
>                  - renesas,r9a09g057h48-ivc
>              - const: renesas,r9a09g057h44-ivc
> 
> 
> Is the latter one right?

This is the preferred style, yes.


> 
> 
>>
>>> +
>>> +  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.
> Fair enough; there's also a clock that the documentation calls "reg_aclk" that goes to the ISP core 
> and I've been calling that one just "aclk" so the "vin_" was to distinguish them...but maybe I 

but there is no other aclk here.

> should just stop trying to follow the documentation's names; how about "reg", "axi" and "isp" for 
> both the clock and reset names?

pclk, aclk and sclk are also acceptable names if this is how they are
called in datasheet, but reg, axi and isp seems better reflect the
purpose of these clocks from this device point of view.

Best regards,
Krzysztof

  reply	other threads:[~2025-06-24 15:41 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
2025-06-24 14:17     ` Dan Scally
2025-06-24 15:41       ` Krzysztof Kozlowski [this message]
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=83755309-230f-4a5d-a658-f5f0d8714e9a@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