Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Tapio Reijonen" <tapio.reijonen@vaisala.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] regulator: dt-bindings: Add MPS MPQ4210
Date: Thu, 10 Sep 2026 09:01:03 +0000	[thread overview]
Message-ID: <20260910090103.98AA11F0089C@smtp.kernel.org> (raw)
In-Reply-To: <20260910-mpq4210-regulator-v1-1-d37e208dfc8d@vaisala.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `mps,fb-voltage-divider` property schema omits `minItems: 2` or an explicit `items` list, allowing incomplete arrays to pass validation.
--

commit 9d4fa47cff6967eb8bf59f67ec44cae66abc946a
Author: Tapio Reijonen <tapio.reijonen@vaisala.com>

regulator: dt-bindings: Add MPS MPQ4210

This commit introduces a new device tree binding for the MPQ4210
buck-boost controller. It specifies standard regulator properties and
adds the mps,fb-voltage-divider property to scale reference voltages.

> diff --git a/Documentation/devicetree/bindings/regulator/mps,mpq4210.yaml b/Documentation/devicetree/bindings/regulator/mps,mpq4210.yaml
> new file mode 100644
> index 0000000000000..e9e7a87e7533d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/mps,mpq4210.yaml

[ ... ]

> +  mps,fb-voltage-divider:
> +    description: An array of two integers containing the resistor values R1
> +      and R2 of the output feedback voltage divider in ohms.
> +    $ref: /schemas/types.yaml#/definitions/uint32-array
> +    maxItems: 2

[Severity: Low]
Does this schema allow incomplete arrays to pass validation?

The property description mentions an array of two integers for R1 and R2,
but without minItems: 2 or an explicit items list, a device tree node with
only one element could silently pass dt_binding_check.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260910-mpq4210-regulator-v1-0-d37e208dfc8d@vaisala.com?part=1

  reply	other threads:[~2026-09-10  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  8:51 [PATCH 0/2] regulator: Add MPS MPQ4210 buck-boost regulator support Tapio Reijonen
2026-09-10  8:51 ` [PATCH 1/2] regulator: dt-bindings: Add MPS MPQ4210 Tapio Reijonen
2026-09-10  9:01   ` sashiko-bot [this message]
2026-09-11  8:45   ` Krzysztof Kozlowski
2026-09-10  8:51 ` [PATCH 2/2] regulator: Add MPS MPQ4210 buck-boost regulator driver Tapio Reijonen
2026-09-11 18:48   ` Uwe Kleine-König
2026-09-10 15:58 ` [PATCH 0/2] regulator: Add MPS MPQ4210 buck-boost regulator support Mark Brown
2026-09-10 15:58 ` Mark Brown

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=20260910090103.98AA11F0089C@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tapio.reijonen@vaisala.com \
    /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