From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Zhiyong Tao <zhiyong.tao@mediatek.com>,
lee.jones@linaro.org, robh+dt@kernel.org, matthias.bgg@gmail.com,
lgirdwood@gmail.com, broonie@kernel.org,
eddie.huang@mediatek.com, a.zummo@towertech.it,
alexandre.belloni@bootlin.com, fshao@chromium.org
Cc: srv_heupstream@mediatek.com, hui.liu@mediatek.com,
tinghan.shen@mediatek.com, hsin-hsiung.wang@mediatek.com,
sean.wang@mediatek.com, macpaul.lin@mediatek.com,
wen.su@mediatek.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: pmic: mt6366: add binding document
Date: Tue, 10 May 2022 12:14:26 +0200 [thread overview]
Message-ID: <ece7675a-a386-0a16-a087-2469758917f7@linaro.org> (raw)
In-Reply-To: <20220510064603.15920-2-zhiyong.tao@mediatek.com>
On 10/05/2022 08:46, Zhiyong Tao wrote:
> From: "Zhiyong.Tao" <zhiyong.tao@mediatek.com>
>
> The commit adds mt6366 binding document.
https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95
>
> Signed-off-by: Zhiyong.Tao <zhiyong.tao@mediatek.com>
> ---
> .../bindings/regulator/mt6366-regulator.yaml | 405 ++++++++++++++++++
> 1 file changed, 405 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/mt6366-regulator.yaml
>
> diff --git a/Documentation/devicetree/bindings/regulator/mt6366-regulator.yaml b/Documentation/devicetree/bindings/regulator/mt6366-regulator.yaml
> new file mode 100644
> index 000000000000..1f125f5ba860
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/mt6366-regulator.yaml
Filename with vendor, so "mediatek,mt6366-regulator.yaml"
> @@ -0,0 +1,405 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/mt6366-regulator.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MT6366 Regulator from MediaTek Integrated
> +
> +maintainers:
> + - Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>
> +
> +description: |
> + List of regulators provided by this controller. It is named
> + according to its regulator type, buck_<name> and ldo_<name>.
> + MT6366 regulators node should be sub node of the MT6397 MFD node.
> +
Missing properties node, missing compatible. How is it supposed to
match? If you plan to use it as part of other binding, please send
entire patchset (including the binding which uses this one).
In current form this looks untestable, unusable.
> +patternProperties:
> + "^buck_v(dram1|core|pa|proc11|proc12|gpu|s2|modem|s1)$":
> + type: object
> + $ref: "regulator.yaml#"
> +
> + properties:
> + regulator-name:
> + pattern: "^v(dram1|core|pa|proc11|proc12|gpu|s2|modem|s1)$"
> +
> + unevaluatedProperties: false
Put this one after $ref (other places as well). Makes it more readable.
> +
> + "^ldo_v(ibr|rf12|usb|camio|efuse|xo22)$":
> + type: object
> + $ref: "regulator.yaml#"
> +
> + properties:
> + regulator-name:
> + pattern: "^v(ibr|rf12|usb|camio|efuse|xo22)$"
> +
> + unevaluatedProperties: false
> +
> + "^ldo_v(rfck|emc|a12|a09|ufs|bbck)$":
> + type: object
> + $ref: "regulator.yaml#"
> +
> + properties:
> + regulator-name:
> + pattern: "^v(rfck|emc|a12|a09|ufs|bbck)$"
> +
> + unevaluatedProperties: false
> +
> + "^ldo_vcn(18|13|33_1_bt|13_1_wifi|33_2_bt|33_2_wifi)$":
No underscores in node names.
> + type: object
> + $ref: "regulator.yaml#"
> +
> + properties:
> + regulator-name:
> + pattern: "^vcn(18|13|33_1_bt|13_1_wifi|33_2_bt|33_2_wifi)$"
> +
> + unevaluatedProperties: false
> +
> + "^ldo_vsram_(proc2|others|md|proc1|others_sshub)$":
No underscores in node names, in all places.
> + type: object
> + $ref: "regulator.yaml#"
> +
> + properties:
> + regulator-name:
> + pattern: "^vsram_(proc2|others|md|proc1|others_sshub)$"
> +
> + unevaluatedProperties: false
> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-05-10 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 6:46 [PATCH v1 0/1] Mediatek MT6366 PMIC patch Zhiyong Tao
2022-05-10 6:46 ` [PATCH] dt-bindings: pmic: mt6366: add binding document Zhiyong Tao
2022-05-10 7:56 ` Rex-BC Chen
2022-05-11 15:36 ` Krzysztof Kozlowski
2022-05-12 2:15 ` Rex-BC Chen
2022-05-10 10:14 ` Krzysztof Kozlowski [this message]
2022-05-10 11:33 ` 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=ece7675a-a386-0a16-a087-2469758917f7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=fshao@chromium.org \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=hui.liu@mediatek.com \
--cc=lee.jones@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-rtc@vger.kernel.org \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tinghan.shen@mediatek.com \
--cc=wen.su@mediatek.com \
--cc=zhiyong.tao@mediatek.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).