From: Rob Herring <robh@kernel.org>
To: Alexandre Mergnat <amergnat@baylibre.com>
Cc: Mark Brown <broonie@kernel.org>,
Chen Zhong <chen.zhong@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Lee Jones <lee@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Fabien Parent <fabien.parent@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Fabien Parent <fparent@baylibre.com>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
devicetree@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v3 3/5] dt-bindings: regulator: Add binding schema for mt6357 regulators
Date: Thu, 20 Oct 2022 20:05:12 -0500 [thread overview]
Message-ID: <20221021010512.GA1974104-robh@kernel.org> (raw)
In-Reply-To: <20221005-mt6357-support-v3-3-7e0bd7c315b2@baylibre.com>
On Thu, Oct 20, 2022 at 06:20:47PM +0200, Alexandre Mergnat wrote:
> From: Fabien Parent <fparent@baylibre.com>
>
> Add YAML schema for the MediaTek MT6357 regulators.
>
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> Signed-off-by: Alexandre Mergnat <amergnat@baylibre.com>
> ---
> .../regulator/mediatek,mt6357-regulator.yaml | 292 +++++++++++++++++++++
> 1 file changed, 292 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/regulator/mediatek,mt6357-regulator.yaml b/Documentation/devicetree/bindings/regulator/mediatek,mt6357-regulator.yaml
> new file mode 100644
> index 000000000000..8dc1245304be
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/mediatek,mt6357-regulator.yaml
> @@ -0,0 +1,292 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/mediatek,mt6357-regulator.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MediaTek MT6357 Regulators
> +
> +maintainers:
> + - Fabien Parent <fabien.parent@linaro.org>
> + - Alexandre Mergnat <amergnat@baylibre.com>
> +
> +description: |
> + The MT6357 PMIC provides 5 BUCK and 29 LDO.
> + Regulators and nodes are named according to the regulator type:
> + buck-<name> and ldo-<name>.
> + MT6357 regulators node should be sub node of the MT6397 MFD node.
> +
> +patternProperties:
> + "^buck-v(core|modem|pa|proc|s1)$":
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description:
> + Properties for single BUCK regulator.
> +
> + required:
> + - regulator-name
> + - regulator-min-microvolt
> + - regulator-max-microvolt
> +
> + "^ldo-v(aud28|aux18|cama|camd|cn18|cn28|cn33-bt|cn33-wifi|dram)$":
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description:
> + Properties for single LDO regulator.
> +
> + required:
> + - regulator-name
> + - regulator-min-microvolt
> + - regulator-max-microvolt
> +
> + "^ldo-v(efuse|emc|ibr|io18|io28|ldo28|mch|rf12|rf18)$":
vf12 and rf18 are covered by regulator-fixed binding.
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description:
> + Properties for single LDO regulator.
> +
> + required:
> + - regulator-name
> + - regulator-min-microvolt
> + - regulator-max-microvolt
> +
> + "^ldo-v(xo22|sim1,sim2|sram-others|sram-proc|usb33|xo22)$":
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description:
> + Properties for single LDO regulator.
> +
> + required:
> + - regulator-name
> + - regulator-min-microvolt
> + - regulator-max-microvolt
> +
> +additionalProperties: false
vfe28 is not listed, and this would cause an error if the schema was
applied, but it is not as Krzysztof pointed out.
The MFD binding really needs to be converted so it can reference this
schema. Otherwise, when it is, then all the issues have to be fixed.
Rob
next prev parent reply other threads:[~2022-10-21 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 16:20 [PATCH v3 0/5] Add MediaTek MT6357 PMIC support Alexandre Mergnat
2022-10-20 16:20 ` [PATCH v3 1/5] dt-bindings: mfd: mt6397: add binding for MT6357 Alexandre Mergnat
2022-10-31 13:53 ` Lee Jones
2022-10-20 16:20 ` [PATCH v3 2/5] dt-bindings: input: mtk-pmic-keys: add binding for MT6357 PMIC Alexandre Mergnat
2022-10-21 8:04 ` AngeloGioacchino Del Regno
2022-10-20 16:20 ` [PATCH v3 3/5] dt-bindings: regulator: Add binding schema for mt6357 regulators Alexandre Mergnat
2022-10-20 16:42 ` Krzysztof Kozlowski
2022-10-21 1:05 ` Rob Herring [this message]
2022-10-20 16:20 ` [PATCH v3 4/5] regulator: add mt6357 regulator Alexandre Mergnat
2022-10-21 8:04 ` AngeloGioacchino Del Regno
2022-10-20 16:20 ` [PATCH v3 5/5] Input: mtk-pmic-keys: add MT6357 support Alexandre Mergnat
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=20221021010512.GA1974104-robh@kernel.org \
--to=robh@kernel.org \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=chen.zhong@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fabien.parent@linaro.org \
--cc=fparent@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mkorpershoek@baylibre.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;
as well as URLs for NNTP newsgroup(s).