From: Mark Brown <broonie@kernel.org>
To: Fabien Parent <fparent@baylibre.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 3/7] dt-bindings: regulator: Add binding schema for mt6357 regulators
Date: Tue, 31 May 2022 15:06:33 +0200 [thread overview]
Message-ID: <YpYS2e1uGmoJGWxr@sirena.org.uk> (raw)
In-Reply-To: <20220531124959.202787-4-fparent@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
On Tue, May 31, 2022 at 02:49:55PM +0200, Fabien Parent wrote:
> + properties:
> + regulator-name:
> + pattern: "^v(core|modem|pa|proc|s1)$"
This is a standard property which you shouldn't need to describe
and should not be imposing any constraints on, the property is
there to provide a system relevant name to the supply provided by
the regulator to aid diagnostics and association with schematics.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-31 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220531124959.202787-1-fparent@baylibre.com>
2022-05-31 12:49 ` [PATCH 1/7] dt-bindings: mfd: mt6397: add binding for MT6357 Fabien Parent
2022-06-05 21:30 ` Rob Herring
2022-06-15 22:24 ` Lee Jones
2022-05-31 12:49 ` [PATCH 2/7] dt-bindings: input: mtk-pmic-keys: add binding for MT6357 PMIC Fabien Parent
2022-06-05 21:30 ` Rob Herring
2022-05-31 12:49 ` [PATCH 3/7] dt-bindings: regulator: Add binding schema for mt6357 regulators Fabien Parent
2022-05-31 13:06 ` Mark Brown [this message]
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=YpYS2e1uGmoJGWxr@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.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=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.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).