From: sashiko-bot@kernel.org
To: "Michael Riesch via B4 Relay"
<devnull+michael.riesch.collabora.com@kernel.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v5 2/8] media: dt-bindings: add rockchip rk3588 vicap
Date: Fri, 22 May 2026 21:40:45 +0000 [thread overview]
Message-ID: <20260522214046.0C9DB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260522-rk3588-vicap-v5-2-d1d1f5265c56@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing `minItems` constraint for `reset-names` in the RK3588 conditional block.
--
commit 63f5bfe4a138b18bc1581d3e98d7e6a10fe7ef3e
Author: Michael Riesch <michael.riesch@collabora.com>
media: dt-bindings: add rockchip rk3588 vicap
This commit adds documentation for the Rockchip RK3588 Video Capture (VICAP)
unit. It generalizes the existing rockchip,rk3568-vicap documentation and
introduces variant-specific constraints.
> diff --git a/Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml b/Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml
> --- a/Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml
> +++ b/Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml
[ ... ]
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: rockchip,rk3588-vicap
> + then:
> + properties:
[ ... ]
> + resets:
> + minItems: 9
> +
> + reset-names:
> + items:
> + - const: arst
> + - const: hrst
> + - const: drst
> + - const: irst0
> + - const: irst1
> + - const: irst2
> + - const: irst3
> + - const: irst4
> + - const: irst5
[Severity: Low]
Does this schema correctly enforce the length of the reset-names array for the
rk3588-vicap variant?
Since the global reset-names definition allows a minimum of 5 items, omitting
minItems: 9 here means a device tree could provide exactly 9 resets but only
5 reset-names and still pass validation. Should this include minItems: 9 to
match the resets property?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260522-rk3588-vicap-v5-0-d1d1f5265c56@collabora.com?part=2
next prev parent reply other threads:[~2026-05-22 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 21:23 [PATCH v5 0/8] media: rockchip: rkcif: add support for rk3588 vicap Michael Riesch via B4 Relay
2026-05-22 21:23 ` [PATCH v5 1/8] Documentation: admin-guide: media: add " Michael Riesch via B4 Relay
2026-05-22 21:23 ` [PATCH v5 2/8] media: dt-bindings: add rockchip " Michael Riesch via B4 Relay
2026-05-22 21:40 ` sashiko-bot [this message]
2026-05-27 8:49 ` Conor Dooley
2026-05-22 21:23 ` [PATCH v5 3/8] media: rockchip: rkcif: add support for rk3588 vicap mipi capture Michael Riesch via B4 Relay
2026-05-22 22:22 ` sashiko-bot
2026-05-22 21:23 ` [PATCH DONOTMERGE v5 4/8] arm64: dts: rockchip: add mipi csi-2 receiver nodes to rk3588 Michael Riesch via B4 Relay
2026-05-22 21:23 ` [PATCH v5 5/8] arm64: dts: rockchip: add vicap node " Michael Riesch via B4 Relay
2026-05-22 21:23 ` [PATCH v5 6/8] arm64: dts: rockchip: add radxa camera 4k on rock 5b+ cam0 Michael Riesch via B4 Relay
2026-05-22 21:23 ` [PATCH v5 7/8] arm64: dts: rockchip: add radxa camera 4k on rock 5b+ cam1 Michael Riesch via B4 Relay
2026-05-22 21:23 ` [PATCH v5 8/8] arm64: defconfig: enable designware mipi csi-2 receiver Michael Riesch via B4 Relay
2026-05-29 11:45 ` (subset) [PATCH v5 0/8] media: rockchip: rkcif: add support for rk3588 vicap Heiko Stuebner
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=20260522214046.0C9DB1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+michael.riesch.collabora.com@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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