From: sashiko-bot@kernel.org
To: "Alexandre Hamamdjian via B4 Relay"
<devnull+azkali.limited.gmail.com@kernel.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: regulator: add SGMicro SGM3804
Date: Mon, 11 May 2026 21:26:17 +0000 [thread overview]
Message-ID: <20260511212618.54424C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260510-sgm3804-v1-1-e5e8799e0aa0@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The DT binding incorrectly models a dual-output regulator (positive and negative) as a single top-level regulator node, preventing independent configuration and referencing of the two outputs.
--
commit db24a4c2f2c96be5ccf7d7d19de93b27ab20e291
Author: Alexandre Hamamdjian <azkali.limited@gmail.com>
dt-bindings: regulator: add SGMicro SGM3804
This commit introduces the device tree binding for the SGMicro SGM3804,
an I2C-controlled charge-pump regulator providing positive and negative
outputs. It also adds the corresponding MAINTAINERS entry.
> diff --git a/Documentation/devicetree/bindings/regulator/sgmicro,sgm3804.yaml b/Documentation/devicetree/bindings/regulator/sgmicro,sgm3804.yaml
> new file mode 100644
> index 0000000000000..f1de17bd5395a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/sgmicro,sgm3804.yaml
> @@ -0,0 +1,60 @@
[ ... ]
> +description:
> + The SGM3804 is an I2C-controlled positive and negative output charge-pump
> + regulator typically used to provide the AVDD and AVEE supplies for display
> + panels. Two reset GPIOs are used to sequence the positive and negative
> + outputs independently.
> +
> +allOf:
> + - $ref: regulator.yaml#
Does this binding correctly model the hardware's dual-output nature?
By applying regulator.yaml# directly to the parent I2C device node without
defining subnodes for the individual outputs, the entire device is treated
as a single regulator.
Since standard properties like regulator-name and regulator-min-microvolt
can only be specified once per node, how can consumers independently configure
or reference the negative rail (AVEE) via phandles?
Should this device be modeled using child subnodes for the outputs (for
example, using patternProperties for outp and outn)?
[ ... ]
> + reset-gpios:
> + minItems: 1
> + maxItems: 2
> + description:
> + Reset/enable GPIOs for the positive (index 0) and, optionally, the
> + negative (index 1) output rails.
If child subnodes are introduced for the positive and negative regulators,
would it be more standard to place an enable-gpios property within each
individual regulator subnode instead of using a shared reset-gpios array on
the parent node?
[ ... ]
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + regulator@3e {
> + compatible = "sgmicro,sgm3804";
> + reg = <0x3e>;
> + reset-gpios = <&tlmm 10 GPIO_ACTIVE_HIGH>,
> + <&tlmm 11 GPIO_ACTIVE_HIGH>;
> + regulator-name = "panel-avdd";
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + };
> + };
The example demonstrates this limitation, as it only configures constraints
for panel-avdd.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260510-sgm3804-v1-0-e5e8799e0aa0@gmail.com?part=1
next prev parent reply other threads:[~2026-05-11 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 16:45 [PATCH 0/2] regulator: add support for SGMicro SGM3804 Alexandre Hamamdjian via B4 Relay
2026-05-10 16:45 ` [PATCH 1/2] dt-bindings: regulator: add " Alexandre Hamamdjian via B4 Relay
2026-05-10 17:45 ` Rob Herring (Arm)
2026-05-11 1:22 ` Mark Brown
2026-05-11 21:26 ` sashiko-bot [this message]
2026-05-10 16:45 ` [PATCH 2/2] regulator: sgm3804: add SGMicro SGM3804 charge-pump regulator driver Alexandre Hamamdjian via B4 Relay
2026-05-11 21:44 ` sashiko-bot
2026-05-11 0:51 ` [PATCH 0/2] regulator: add support for SGMicro SGM3804 Mark Brown
2026-05-11 8:11 ` Neil Armstrong
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=20260511212618.54424C2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+azkali.limited.gmail.com@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko@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