Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Neil Armstrong" <neil.armstrong@linaro.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/2] regulator: dt-bindings: document the SGM3804 Dual Output regulator
Date: Fri, 22 May 2026 13:19:37 +0000	[thread overview]
Message-ID: <20260522131937.A38F91F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260522-topic-sm8650-ayaneo-pocket-s2-sgm3804-v5-1-bd6b1c300ecc@linaro.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `enable-gpios` property is incorrectly marked as strictly required and lacks a `maxItems: 1` constraint.
--

commit f50493aa554fa5cd96589605f9a49a0134ff39ab
Author: Neil Armstrong <neil.armstrong@linaro.org>

regulator: dt-bindings: document the SGM3804 Dual Output regulator

This commit documents the sgm3804 single inductor dual output buck/boost
converter. It provides bindings for the positive and negative power rails,
including configurable voltages and active discharge functions.

> diff --git a/Documentation/devicetree/bindings/regulator/sgmicro,sgm3804.yaml b/Documentation/devicetree/bindings/regulator/sgmicro,sgm3804.yaml
> new file mode 100644
> index 0000000000000..3716eaf81aa99
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/sgmicro,sgm3804.yaml

[ ... ]

> +patternProperties:
> +  "^(pos|neg)$":
> +    type: object
> +    $ref: regulator.yaml#
> +
> +    properties:
> +      enable-gpios: true

[Severity: Medium]
Should enable-gpios have a maxItems constraint here? The core regulator.yaml
schema does not define a maxItems limit for enable-gpios, so setting this to
true allows an arbitrary number of gpios to be specified in the device tree
instead of a single enable pin per output.

> +
> +    unevaluatedProperties: false
> +
> +    required:
> +      - enable-gpios

[Severity: Medium]
Is it strictly necessary to require enable-gpios for these child nodes? If a
board design hardwires the hardware enable pins to an always-on supply to
conserve processor pins, the regulator would be constantly powered but still
configurable via i2c. Marking enable-gpios as strictly required will cause a
schema validation failure for those valid hardware configurations, even if
the driver currently expects the pins to be present.

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260522-topic-sm8650-ayaneo-pocket-s2-sgm3804-v5-0-bd6b1c300ecc@linaro.org?part=1

  reply	other threads:[~2026-05-22 13:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 13:09 [PATCH v5 0/2] regulator: add support for SGM3804 Dual Output driver Neil Armstrong
2026-05-22 13:09 ` [PATCH v5 1/2] regulator: dt-bindings: document the SGM3804 Dual Output regulator Neil Armstrong
2026-05-22 13:19   ` sashiko-bot [this message]
2026-05-22 13:09 ` [PATCH v5 2/2] regulator: add SGM3804 Dual Output driver Neil Armstrong
2026-05-22 13:50   ` sashiko-bot
2026-05-24 22:35 ` [PATCH v5 0/2] regulator: add support for " 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=20260522131937.A38F91F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=neil.armstrong@linaro.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