From: Michael Riesch <michael.riesch@collabora.com>
To: Rob Herring <robh@kernel.org>
Cc: "Mehdi Djait" <mehdi.djait@linux.intel.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Kever Yang" <kever.yang@rock-chips.com>,
"Jagan Teki" <jagan@amarulasolutions.com>,
"Кузнецов Михаил" <mai.kuznetsov.misha@gmail.com>,
"Charalampos Mitrodimas" <charmitro@posteo.net>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
"Collabora Kernel Team" <kernel@collabora.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
"Conor Dooley" <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 2/8] media: dt-bindings: add rockchip rk3588 vicap
Date: Wed, 13 May 2026 16:47:25 +0200 [thread overview]
Message-ID: <f59370e6-7921-4227-a8bf-ccbb9f03da23@collabora.com> (raw)
In-Reply-To: <20260513124858.GA585254-robh@kernel.org>
Hi Rob,
On 5/13/26 14:48, Rob Herring wrote:
> On Fri, May 08, 2026 at 09:31:45PM +0200, Michael Riesch wrote:
>>[...]
>> properties:
>> compatible:
>> - const: rockchip,rk3568-vicap
>> + enum:
>> + - rockchip,rk3568-vicap
>> + - rockchip,rk3588-vicap
>>
>> reg:
>> maxItems: 1
>> @@ -26,37 +32,23 @@ properties:
>> maxItems: 1
>>
>> clocks:
>> - items:
>> - - description: ACLK
>> - - description: HCLK
>> - - description: DCLK
>> - - description: ICLK
>> + minItems: 4
>> + maxItems: 5
>>
>> clock-names:
>> - items:
>> - - const: aclk
>> - - const: hclk
>> - - const: dclk
>> - - const: iclk
>
> Just keep this here and add iclk1 on the end along with 'minItems: 4'.
Just to make sure I get it right: The names on the RK3588 would then be
aclk, hclk, dclk, iclk, iclk1
?
I liked that zero. But OK.
Looking into the future, the RK3576 downstream has aclk, hclk, dclk,
iclk{0-4} [0]. Again, if we rename "iclk0" -> "iclk", we can do the same
trick.
However, the RK3562 downstream has aclk, hclk, dclk, csirx{0-3} [1]. We
could rename those to iclk, as those iclks seem to refer to the CSI
hosts/receivers.
Yeah, should work I think. Will update in v5.
Best regards,
Michael
>
>> + minItems: 4
>> + maxItems: 5
>
[0]
https://github.com/rockchip-linux/kernel/blob/develop-6.6/arch/arm64/boot/dts/rockchip/rk3576.dtsi#L3342
[1]
https://github.com/rockchip-linux/kernel/blob/develop-6.6/arch/arm64/boot/dts/rockchip/rk3562.dtsi#L2073
next prev parent reply other threads:[~2026-05-13 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 19:31 [PATCH v4 0/8] media: rockchip: rkcif: add support for rk3588 vicap Michael Riesch via B4 Relay
2026-05-08 19:31 ` [PATCH v4 1/8] Documentation: admin-guide: media: add " Michael Riesch via B4 Relay
2026-05-08 19:31 ` [PATCH v4 2/8] media: dt-bindings: add rockchip " Michael Riesch via B4 Relay
2026-05-13 12:48 ` Rob Herring
2026-05-13 14:47 ` Michael Riesch [this message]
2026-05-08 19:31 ` [PATCH v4 3/8] media: rockchip: rkcif: add support for rk3588 vicap mipi capture Michael Riesch via B4 Relay
2026-05-08 19:31 ` [PATCH DONOTMERGE v4 4/8] arm64: dts: rockchip: add mipi csi-2 receiver nodes to rk3588 Michael Riesch via B4 Relay
2026-05-08 19:31 ` [PATCH v4 5/8] arm64: dts: rockchip: add vicap node " Michael Riesch via B4 Relay
2026-05-08 19:31 ` [PATCH v4 6/8] arm64: dts: rockchip: add radxa camera 4k on rock 5b+ cam0 Michael Riesch via B4 Relay
2026-05-08 19:31 ` [PATCH v4 7/8] arm64: dts: rockchip: add radxa camera 4k on rock 5b+ cam1 Michael Riesch via B4 Relay
2026-05-08 19:31 ` [PATCH v4 8/8] arm64: defconfig: enable designware mipi csi-2 receiver Michael Riesch via B4 Relay
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=f59370e6-7921-4227-a8bf-ccbb9f03da23@collabora.com \
--to=michael.riesch@collabora.com \
--cc=charmitro@posteo.net \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mai.kuznetsov.misha@gmail.com \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=nicolas.dufresne@collabora.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sebastian.reichel@collabora.com \
/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