From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: linux-mediatek@lists.infradead.org, lee@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, matthias.bgg@gmail.com,
lgirdwood@gmail.com, broonie@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@collabora.com,
wenst@chromium.org, igor.belwon@mentallysanemainliners.org
Subject: Re: [PATCH v8 1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators
Date: Thu, 9 Oct 2025 14:18:52 -0500 [thread overview]
Message-ID: <20251009191852.GA2947598-robh@kernel.org> (raw)
In-Reply-To: <20251003091158.26748-2-angelogioacchino.delregno@collabora.com>
On Fri, Oct 03, 2025 at 11:11:50AM +0200, AngeloGioacchino Del Regno wrote:
> Add bindings for the regulators found in the MediaTek MT6316 PMIC,
> usually found in board designs using the MT6991 Dimensity 9400 and
> on MT8196 Kompanio SoC for Chromebooks.
>
> This chip is fully controlled by SPMI and has multiple variants
> providing different phase configurations.
>
> Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> .../regulator/mediatek,mt6316b-regulator.yaml | 80 +++++++++++++++++++
> .../regulator/mediatek,mt6316c-regulator.yaml | 80 +++++++++++++++++++
> .../regulator/mediatek,mt6316d-regulator.yaml | 79 ++++++++++++++++++
> 3 files changed, 239 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6316b-regulator.yaml
> create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6316c-regulator.yaml
> create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6316d-regulator.yaml
>
> diff --git a/Documentation/devicetree/bindings/regulator/mediatek,mt6316b-regulator.yaml b/Documentation/devicetree/bindings/regulator/mediatek,mt6316b-regulator.yaml
> new file mode 100644
> index 000000000000..53d2c9913e55
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/mediatek,mt6316b-regulator.yaml
> @@ -0,0 +1,80 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/mediatek,mt6316b-regulator.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MediaTek MT6316 BP/VP SPMI PMIC Regulators
> +
> +maintainers:
> + - AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> +
> +description:
> + The MediaTek MT6316BP/VP PMICs are fully controlled by SPMI interface, both
> + feature four step-down DC/DC (buck) converters, and provides 2+2 Phases,
> + joining Buck 1+2 for the first phase, and Buck 3+4 for the second phase.
> +
> +properties:
> + compatible:
> + const: mediatek,mt6316b-regulator
> +
> + reg:
> + maxItems: 1
> +
> + '#address-cells':
> + const: 0
You don't have any child nodes with addresses. Drop.
> +
> +patternProperties:
> + "^vbuck(12|34)$":
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + properties:
> + regulator-allowed-modes:
> + description: |
> + Allowed Buck regulator operating modes allowed. Valid values below.
> + 0 - Normal mode with automatic power saving, reducing the switching
> + frequency when light load conditions are detected
> + 1 - Forced Continuous Conduction mode (FCCM) for improved voltage
> + regulation accuracy with constant switching frequency but lower
> + regulator efficiency
> + 2 - Forced Low Power mode for improved regulator efficiency, used
> + when no heavy load is expected, will shut down unnecessary IP
> + blocks and secondary phases to reduce quiescent current.
> + This mode does not limit the maximum output current but unless
> + only a light load is applied, there will be regulation accuracy
> + and efficiency losses.
> + maxItems: 3
If you can only specify all the modes, why do you need it? Perhaps you
want 'minItems: 1' as well?
> + items:
> + enum: [ 0, 1, 2 ]
> +
> +required:
> + - compatible
> + - reg
> + - '#address-cells'
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/spmi/spmi.h>
> +
> + spmi {
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + pmic@8 {
> + compatible = "mediatek,mt6316b-regulator";
> + reg = <0x8 SPMI_USID>;
> + #address-cells = <0>;
> +
> + vbuck12 {
> + regulator-name = "dvdd_core";
> + regulator-min-microvolt = <450000>;
> + regulator-max-microvolt = <965000>;
> + regulator-allowed-modes = <0 1 2>;
> + regulator-enable-ramp-delay = <256>;
> + };
> + };
> + };
> +...
next prev parent reply other threads:[~2025-10-09 19:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 9:11 [PATCH v8 0/9] Add support MT6316/6363/MT6373 PMICs regulators and MFD AngeloGioacchino Del Regno
2025-10-03 9:11 ` [PATCH v8 1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators AngeloGioacchino Del Regno
2025-10-09 19:18 ` Rob Herring [this message]
2025-10-03 9:11 ` [PATCH v8 2/9] regulator: Add support for MediaTek MT6316 SPMI " AngeloGioacchino Del Regno
2025-10-10 21:17 ` kernel test robot
2025-10-03 9:11 ` [PATCH v8 3/9] dt-bindings: regulator: Document MediaTek MT6363 " AngeloGioacchino Del Regno
2025-10-03 9:11 ` [PATCH v8 4/9] regulator: Add support for MediaTek MT6363 SPMI " AngeloGioacchino Del Regno
2025-10-09 14:41 ` Nicolas Frattaroli
2025-10-14 11:35 ` AngeloGioacchino Del Regno
2025-10-14 12:35 ` Mark Brown
2025-10-03 9:11 ` [PATCH v8 5/9] dt-bindings: regulator: Document MediaTek MT6373 " AngeloGioacchino Del Regno
2025-10-09 19:21 ` Rob Herring (Arm)
2025-10-03 9:11 ` [PATCH v8 6/9] regulator: Add support for MediaTek MT6373 SPMI " AngeloGioacchino Del Regno
2025-10-11 5:32 ` kernel test robot
2025-10-03 9:11 ` [PATCH v8 7/9] dt-bindings: iio: adc: mt6359: Allow reg for SPMI PMICs AuxADC AngeloGioacchino Del Regno
2025-10-03 9:11 ` [PATCH v8 8/9] dt-bindings: mfd: Add binding for MediaTek MT6363 series SPMI PMIC AngeloGioacchino Del Regno
2025-10-09 19:24 ` Rob Herring
2025-10-03 9:11 ` [PATCH v8 9/9] drivers: mfd: Add support for MediaTek SPMI PMICs and MT6363/73 AngeloGioacchino Del Regno
2025-10-09 20:15 ` Nicolas Frattaroli
2025-10-23 13:53 ` Lee Jones
2025-10-24 6:03 ` AngeloGioacchino Del Regno
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=20251009191852.GA2947598-robh@kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=igor.belwon@mentallysanemainliners.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=wenst@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).