Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ramshouriesh R" <rshouriesh@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v5 1/2] media: dt-bindings: Add Himax HM1092 NIR sensor
Date: Thu, 09 Jul 2026 08:18:16 +0000	[thread overview]
Message-ID: <20260709081816.A3A941F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260709-hm1092-driver-v5-1-a1f5baa6fe08@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `data-lanes` property is unconstrained in the MIPI CSI-2 endpoint, allowing invalid hardware configurations to pass validation.
--

--- Patch [1]: [PATCH v5 1/2] media: dt-bindings: Add Himax HM1092 NIR sensor ---
commit c0fd35985ccc449c8ccfd7a8009b9fa4c8298ef0
Author: Ramshouriesh R <rshouriesh@gmail.com>

media: dt-bindings: Add Himax HM1092 NIR sensor

This commit adds a device tree binding schema for the Himax HM1092, a 1
megapixel monochrome near-infrared CMOS image sensor. The sensor streams
10-bit RAW data over a single MIPI CSI-2 data lane.

> diff --git a/Documentation/devicetree/bindings/media/i2c/himax,hm1092.yaml b/Documentation/devicetree/bindings/media/i2c/himax,hm1092.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/himax,hm1092.yaml

[ ... ]

> +  port:
> +    $ref: /schemas/graph.yaml#/$defs/port-base
> +    additionalProperties: false
> +
> +    properties:
> +      endpoint:
> +        $ref: /schemas/media/video-interfaces.yaml#
> +        unevaluatedProperties: false
> +
> +        required:
> +          - link-frequencies

[Severity: Low]
The commit message mentions that the sensor streams over a single MIPI
CSI-2 data lane. Should this endpoint definition include a constraint for
data-lanes (for example, maxItems: 1) to prevent invalid hardware
configurations with multiple lanes from passing schema validation?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260709-hm1092-driver-v5-0-a1f5baa6fe08@gmail.com?part=1

  reply	other threads:[~2026-07-09  8:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  8:11 [PATCH v5 0/2] media: Add Himax HM1092 mono NIR sensor driver Ramshouriesh R
2026-07-09  8:11 ` [PATCH v5 1/2] media: dt-bindings: Add Himax HM1092 NIR sensor Ramshouriesh R
2026-07-09  8:18   ` sashiko-bot [this message]
2026-07-09  8:11 ` [PATCH v5 2/2] media: i2c: hm1092: add Himax HM1092 mono NIR sensor driver Ramshouriesh R
2026-07-09  8:22   ` 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=20260709081816.A3A941F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rshouriesh@gmail.com \
    --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