Re: [PATCH v2 2/9] media: dt-bindings: add rockchip rk3588 vicap

From: Conor Dooley

Date: Wed Mar 18 2026 - 14:21:34 EST


On Tue, Mar 17, 2026 at 10:32:20AM +0100, Michael Riesch via B4 Relay wrote:
> From: Michael Riesch <michael.riesch@xxxxxxxxxxxxx>
>
> Add documentation for the Rockchip RK3588 Video Capture (VICAP) unit.
> To that end, make the existing rockchip,rk3568-vicap documentation
> more general and introduce variant specific constraints.
>
> Signed-off-by: Michael Riesch <michael.riesch@xxxxxxxxxxxxx>
> ---
> .../bindings/media/rockchip,rk3568-vicap.yaml | 191 ++++++++++++++++++---
> 1 file changed, 167 insertions(+), 24 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml b/Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml
> index 18cd0a5a5318..15a889ff8e52 100644
> --- a/Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml
> +++ b/Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml
> @@ -15,9 +15,15 @@ description:
> the data from camera sensors, video decoders, or other companion ICs and
> transfers it into system main memory by AXI bus.
>
> + The Rockchip RK3588 Video Capture (VICAP) is similar to its RK3568
> + counterpart, but features six MIPI CSI-2 ports and additional connections
> + to the image signal processor (ISP) blocks.
> +
> 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
> + minItems: 4
> + maxItems: 5
>
> iommus:
> maxItems: 1
>
> resets:
> - items:
> - - description: ARST
> - - description: HRST
> - - description: DRST
> - - description: PRST
> - - description: IRST
> + minItems: 5
> + maxItems: 9
>
> reset-names:
> - items:
> - - const: arst
> - - const: hrst
> - - const: drst
> - - const: prst
> - - const: irst
> + minItems: 5
> + maxItems: 9

> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: rockchip,rk3568-vicap
> + then:
> + properties:
> + clocks:
> + minItems: 4
> + maxItems: 4

Anything here that repeats the outermost constraint should be dropped,
so no minItems here..

> +
> + clock-names:
> + items:
> + - const: aclk
> + - const: hclk
> + - const: dclk
> + - const: iclk
> +
> + resets:
> + minItems: 5
> + maxItems: 5

...or here...

> +
> + reset-names:
> + items:
> + - const: arst
> + - const: hrst
> + - const: drst
> + - const: prst
> + - const: irst

> + - if:
> + properties:
> + compatible:
> + contains:
> + const: rockchip,rk3588-vicap
> + then:
> + properties:
> + clocks:
> + minItems: 5
> + maxItems: 5

...or maxItems here...

> +
> + clock-names:
> + items:
> + - const: aclk
> + - const: hclk
> + - const: dclk
> + - const: iclk0

> + - const: iclk1
> +
> + resets:
> + minItems: 9
> + maxItems: 9

...or here.

> +
> + reset-names:
> + items:
> + - const: arst
> + - const: hrst
> + - const: drst
> + - const: irst0

Were you willing to reuse "irst" for the 0th irst, all the repetition
wouldn't be needed. I assume it represents the reset for the port at
address 0, so it wouldn't even be a different meaning on each device.

> + - const: irst1
> + - const: irst2
> + - const: irst3
> + - const: irst4
> + - const: irst5
> +
> additionalProperties: false
>
> examples:
>
> --
> 2.39.5
>
>

Attachment: signature.asc
Description: PGP signature