From: sashiko-bot@kernel.org
To: "Herman van Hazendonk via B4 Relay"
<devnull+github.com.herrie.org@kernel.org>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: media: i2c: add aptina,mt9m113
Date: Fri, 05 Jun 2026 03:49:34 +0000 [thread overview]
Message-ID: <20260605034934.F15F11F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260605-submit-media-mt9m113-v2-1-de1cc807f4cf@herrie.org>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] Missing schema length constraints for `reset-gpios` and `powerdown-gpios` arrays.
- [Low] Binding strictly rejects standard camera properties by not referencing `video-interface-devices.yaml`.
--
commit 63f988e66ed5aa2849614f19a1ca36bc01146bb7
Author: Herman van Hazendonk <github.com@herrie.org>
dt-bindings: media: i2c: add aptina,mt9m113
Adds a new device tree binding for the Aptina MT9M113 1.3 megapixel image
sensor. The binding details the I2C address, optional GPIOs, regulators, and
the MIPI CSI-2 port configuration.
> diff --git a/Documentation/devicetree/bindings/media/i2c/aptina,mt9m113.yaml b/Documentation/devicetree/bindings/media/i2c/aptina,mt9m113.yaml
> new file mode 100644
> index 0000000000000..7fa7cb2fedf96
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/aptina,mt9m113.yaml
> @@ -0,0 +1,127 @@
[ ... ]
> + vaa-supply:
> + description:
> + Analog voltage supply, 2.8V
> +
> + reset-gpios:
> + description: |-
> + Reference to the GPIO connected to the RESET_BAR pin, if any (active
> + low).
> +
> + powerdown-gpios:
> + description: |-
> + Reference to the GPIO connected to the STANDBY/PWDN pin, if any (active
> + high). When asserted, the sensor enters low-power standby mode.
[Severity: Low]
Should these properties include a maxItems: 1 constraint?
In Device Tree schemas, properties with the -gpios suffix map to arrays.
Without an explicit maximum length, dt-schema validation might allow arrays
of any length to pass. Since the hardware has exactly one reset pin and one
standby pin, enforcing a limit of 1 seems appropriate here to ensure strict
validation.
> +
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
[ ... ]
> +required:
> + - compatible
> + - reg
> + - clocks
> + - vdd-supply
> + - vddio-supply
> + - vaa-supply
> + - port
> +
> +additionalProperties: false
[Severity: Low]
Does this schema need a reference to
/schemas/media/video-interface-devices.yaml# before strictly disallowing
additional properties?
Camera sensors frequently require standard physical properties like rotation,
orientation, or flash-leds to describe how they are mounted on the board.
Setting additionalProperties to false without including the standard video
interface device schema will erroneously reject valid device trees that use
these common properties.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260605-submit-media-mt9m113-v2-0-de1cc807f4cf@herrie.org?part=1
next prev parent reply other threads:[~2026-06-05 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 3:38 [PATCH v2 0/2] media: i2c: add Aptina MT9M113 SoC sensor driver Herman van Hazendonk via B4 Relay
2026-06-05 3:38 ` [PATCH v2 1/2] dt-bindings: media: i2c: add aptina,mt9m113 Herman van Hazendonk via B4 Relay
2026-06-05 3:49 ` sashiko-bot [this message]
2026-06-05 3:38 ` [PATCH v2 2/2] media: i2c: add Aptina MT9M113 1.3 Mpx SoC sensor driver Herman van Hazendonk via B4 Relay
2026-06-05 3:53 ` 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=20260605034934.F15F11F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+github.com.herrie.org@kernel.org \
--cc=linux-media@vger.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