From: sashiko-bot@kernel.org
To: "Jacopo Mondi" <jacopo.mondi@ideasonboard.com>
Cc: conor+dt@kernel.org, robh@kernel.org, media-ci@linuxtv.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v11 1/2] dt-bindings: media: i2c: Add mira220 image sensor
Date: Fri, 31 Jul 2026 15:37:06 +0000 [thread overview]
Message-ID: <20260731153706.D14A31F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260731-mira220-v11-1-1295fe17021d@ideasonboard.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Removing `anyOf` from `data-lanes` without explicitly adding `minItems: 1` implicitly restricts `data-lanes` to strictly 2 lanes, rejecting valid 1-lane configurations.
--
--- Patch [1]: [PATCH v11 1/2] dt-bindings: media: i2c: Add mira220 image sensor ---
commit d966c6286995396b61812a3a1c5b7c1683f0cbf3
Author: Philippe Baetens <philippebaetens@gmail.com>
Subject: dt-bindings: media: i2c: Add mira220 image sensor
Adds device tree bindings for the AMSOSRAM Mira220 image sensor.
> diff --git a/Documentation/devicetree/bindings/media/i2c/ams,mira220.yaml b/Documentation/devicetree/bindings/media/i2c/ams,mira220.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ams,mira220.yaml
[ ... ]
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + data-lanes:
> + items:
> + - const: 1
> + - const: 2
[Severity: Low]
Does this configuration implicitly restrict data-lanes to strictly 2 lanes?
By defining items as a two-element array without overriding minItems, dtschema
automatically infers minItems: 2. This overrides the minItems: 1 inherited
from video-interfaces.yaml, which causes valid 1-lane device tree
configurations like data-lanes = <1>; to fail schema validation.
Could an explicit minItems: 1 be added to allow 1-lane configurations?
> +
> + required:
> + - data-lanes
> + - link-frequencies
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260731-mira220-v11-0-1295fe17021d@ideasonboard.com?part=1
next prev parent reply other threads:[~2026-07-31 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 15:28 [PATCH v11 0/2] media: i2c: Add driver for Mira220 Jacopo Mondi
2026-07-31 15:28 ` [PATCH v11 1/2] dt-bindings: media: i2c: Add mira220 image sensor Jacopo Mondi
2026-07-31 15:37 ` sashiko-bot [this message]
2026-07-31 15:28 ` [PATCH v11 2/2] media: i2c: Add driver for AMS-OSRAM Mira220 Jacopo Mondi
2026-07-31 15:47 ` sashiko-bot
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=20260731153706.D14A31F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=media-ci@linuxtv.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