From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: djakov@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, matthias.bgg@gmail.com, lgirdwood@gmail.com,
broonie@kernel.org, keescook@chromium.org, gustavoars@kernel.org,
henryc.chen@mediatek.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, kernel@collabora.com,
wenst@chromium.org, amergnat@baylibre.com
Subject: Re: [PATCH v2 1/7] dt-bindings: regulator: Add bindings for MediaTek DVFSRC Regulators
Date: Wed, 17 Apr 2024 09:52:38 -0500 [thread overview]
Message-ID: <20240417145238.GA2348962-robh@kernel.org> (raw)
In-Reply-To: <20240417091442.170505-2-angelogioacchino.delregno@collabora.com>
On Wed, Apr 17, 2024 at 11:14:36AM +0200, AngeloGioacchino Del Regno wrote:
> The Dynamic Voltage and Frequency Scaling Resource Collector Regulators
> are controlled with votes to the DVFSRC hardware.
>
> This adds support for the regulators found in MT6873, MT8183, MT8192
> and MT8195 SoCs.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> .../mediatek,mt6873-dvfsrc-regulator.yaml | 71 +++++++++++++++++++
> 1 file changed, 71 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6873-dvfsrc-regulator.yaml
>
> diff --git a/Documentation/devicetree/bindings/regulator/mediatek,mt6873-dvfsrc-regulator.yaml b/Documentation/devicetree/bindings/regulator/mediatek,mt6873-dvfsrc-regulator.yaml
> new file mode 100644
> index 000000000000..446f1dab4d2e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/mediatek,mt6873-dvfsrc-regulator.yaml
> @@ -0,0 +1,71 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/mediatek,mt6873-dvfsrc-regulator.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MediaTek DVFSRC-controlled Regulators
> +
> +description:
> + The Dynamic Voltage and Frequency Scaling Resource Collector Regulators
> + are controlled with votes to the DVFSRC hardware.
> +
> +maintainers:
> + - AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> +
> +properties:
> + compatible:
> + enum:
> + - mediatek,mt6873-dvfsrc-regulator
> + - mediatek,mt8183-dvfsrc-regulator
> + - mediatek,mt8192-dvfsrc-regulator
> + - mediatek,mt8195-dvfsrc-regulator
> +
> + reg:
> + maxItems: 1
> +
> + dvfsrc-vcore:
> + description: DVFSRC-controlled SoC Vcore regulator
> + $ref: regulator.yaml#
unevaluatedProperties: false
> +
> + dvfsrc-vscp:
> + description: DVFSRC-controlled System Control Processor regulator
> + $ref: regulator.yaml#
ditto
> +
> +required:
> + - compatible
'reg' is never optional. And how is no regulators at all valid?
> +
> +additionalProperties: false
> +
> +examples:
> + - |
Drop the example here. Just one complete example in the MFD doc.
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + system-controller@10012000 {
> + compatible = "mediatek,mt8195-dvfsrc";
> + reg = <0 0x10012000 0 0x1000>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + regulators@0 {
> + compatible = "mediatek,mt8195-dvfsrc-regulator";
> + reg = <0>;
What does 'reg' value represent here? 0 and 1 seem pretty much made up.
> +
> + dvfsrc_vcore: dvfsrc-vcore {
> + regulator-name = "dvfsrc-vcore";
> + regulator-min-microvolt = <550000>;
> + regulator-max-microvolt = <750000>;
> + regulator-always-on;
> + };
> +
> + dvfsrc_vscp: dvfsrc-vscp {
> + regulator-name = "dvfsrc-vscp";
> + regulator-min-microvolt = <550000>;
> + regulator-max-microvolt = <750000>;
> + regulator-always-on;
> + };
> + };
> + };
> + };
> --
> 2.44.0
>
next prev parent reply other threads:[~2024-04-17 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 9:14 [PATCH v2 0/7] MediaTek DVFSRC Bus Bandwidth and Regulator knobs AngeloGioacchino Del Regno
2024-04-17 9:14 ` [PATCH v2 1/7] dt-bindings: regulator: Add bindings for MediaTek DVFSRC Regulators AngeloGioacchino Del Regno
2024-04-17 14:46 ` Rob Herring
2024-04-17 15:32 ` AngeloGioacchino Del Regno
2024-04-17 14:52 ` Rob Herring [this message]
2024-04-17 15:39 ` AngeloGioacchino Del Regno
2024-04-17 19:12 ` Rob Herring
2024-04-18 7:42 ` AngeloGioacchino Del Regno
2024-04-17 9:14 ` [PATCH v2 2/7] dt-bindings: interconnect: Add MediaTek EMI Interconnect bindings AngeloGioacchino Del Regno
2024-04-17 14:46 ` Rob Herring
2024-04-17 14:54 ` Rob Herring
2024-04-17 15:32 ` AngeloGioacchino Del Regno
2024-04-17 19:14 ` Rob Herring
2024-04-18 7:43 ` AngeloGioacchino Del Regno
2024-04-17 9:14 ` [PATCH v2 3/7] dt-bindings: soc: mediatek: Add DVFSRC bindings for MT8183 and MT8195 AngeloGioacchino Del Regno
2024-04-17 9:14 ` [PATCH v2 4/7] soc: mediatek: Add MediaTek DVFS Resource Collector (DVFSRC) driver AngeloGioacchino Del Regno
2024-04-17 9:14 ` [PATCH v2 5/7] regulator: Remove mtk-dvfsrc-regulator.c AngeloGioacchino Del Regno
2024-04-17 9:14 ` [PATCH v2 6/7] regulator: Add refactored mtk-dvfsrc-regulator driver AngeloGioacchino Del Regno
2024-04-17 9:14 ` [PATCH v2 7/7] interconnect: mediatek: Add MediaTek MT8183/8195 EMI Interconnect driver 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=20240417145238.GA2348962-robh@kernel.org \
--to=robh@kernel.org \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=gustavoars@kernel.org \
--cc=henryc.chen@mediatek.com \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.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=linux-pm@vger.kernel.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