From: Anand K Mistry <amistry@google.com>
To: linux-mediatek@lists.infradead.org
Cc: hsin-hsiung.wang@mediatek.com, drinkcat@chromium.org,
Anand K Mistry <amistry@google.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/4] dt-bindings: regulator: mt6397: Document valid modes
Date: Thu, 2 Jul 2020 16:23:18 +1000 [thread overview]
Message-ID: <20200702162231.v2.2.I0a814b246cfe47f8dd1e25553ee881cbcfd0d8eb@changeid> (raw)
In-Reply-To: <20200702062320.2903147-1-amistry@google.com>
Document valid mode values for BUCK regulators.
Signed-off-by: Anand K Mistry <amistry@google.com>
---
Changes in v2: None
.../devicetree/bindings/regulator/mt6397-regulator.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt b/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
index 01141fb00875..c080086d3e62 100644
--- a/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
+++ b/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
@@ -16,6 +16,9 @@ LDO:
ldo_vemc3v3, ldo_vgp1, ldo_vgp2, ldo_vgp3, ldo_vgp4, ldo_vgp5, ldo_vgp6,
ldo_vibr
+BUCK regulators can set regulator-initial-mode and regulator-allowed-modes to
+values specified in dt-bindings/regulator/mediatek,mt6397-regulator.h
+
Example:
pmic {
compatible = "mediatek,mt6397";
--
2.27.0.212.ge8ba1cc988-goog
WARNING: multiple messages have this Message-ID (diff)
From: Anand K Mistry <amistry@google.com>
To: linux-mediatek@lists.infradead.org
Cc: devicetree@vger.kernel.org, drinkcat@chromium.org,
Anand K Mistry <amistry@google.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
hsin-hsiung.wang@mediatek.com
Subject: [PATCH v2 2/4] dt-bindings: regulator: mt6397: Document valid modes
Date: Thu, 2 Jul 2020 16:23:18 +1000 [thread overview]
Message-ID: <20200702162231.v2.2.I0a814b246cfe47f8dd1e25553ee881cbcfd0d8eb@changeid> (raw)
In-Reply-To: <20200702062320.2903147-1-amistry@google.com>
Document valid mode values for BUCK regulators.
Signed-off-by: Anand K Mistry <amistry@google.com>
---
Changes in v2: None
.../devicetree/bindings/regulator/mt6397-regulator.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt b/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
index 01141fb00875..c080086d3e62 100644
--- a/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
+++ b/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
@@ -16,6 +16,9 @@ LDO:
ldo_vemc3v3, ldo_vgp1, ldo_vgp2, ldo_vgp3, ldo_vgp4, ldo_vgp5, ldo_vgp6,
ldo_vibr
+BUCK regulators can set regulator-initial-mode and regulator-allowed-modes to
+values specified in dt-bindings/regulator/mediatek,mt6397-regulator.h
+
Example:
pmic {
compatible = "mediatek,mt6397";
--
2.27.0.212.ge8ba1cc988-goog
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Anand K Mistry <amistry@google.com>
To: linux-mediatek@lists.infradead.org
Cc: devicetree@vger.kernel.org, drinkcat@chromium.org,
Anand K Mistry <amistry@google.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
hsin-hsiung.wang@mediatek.com
Subject: [PATCH v2 2/4] dt-bindings: regulator: mt6397: Document valid modes
Date: Thu, 2 Jul 2020 16:23:18 +1000 [thread overview]
Message-ID: <20200702162231.v2.2.I0a814b246cfe47f8dd1e25553ee881cbcfd0d8eb@changeid> (raw)
In-Reply-To: <20200702062320.2903147-1-amistry@google.com>
Document valid mode values for BUCK regulators.
Signed-off-by: Anand K Mistry <amistry@google.com>
---
Changes in v2: None
.../devicetree/bindings/regulator/mt6397-regulator.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt b/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
index 01141fb00875..c080086d3e62 100644
--- a/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
+++ b/Documentation/devicetree/bindings/regulator/mt6397-regulator.txt
@@ -16,6 +16,9 @@ LDO:
ldo_vemc3v3, ldo_vgp1, ldo_vgp2, ldo_vgp3, ldo_vgp4, ldo_vgp5, ldo_vgp6,
ldo_vibr
+BUCK regulators can set regulator-initial-mode and regulator-allowed-modes to
+values specified in dt-bindings/regulator/mediatek,mt6397-regulator.h
+
Example:
pmic {
compatible = "mediatek,mt6397";
--
2.27.0.212.ge8ba1cc988-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-02 6:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 6:23 [PATCH v2 0/4] regulator: mt6397: Implement of_map_mode regulator_desc function Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 6:23 ` [PATCH v2 1/4] regulator: mt6397: Move buck modes into header file Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry [this message]
2020-07-02 6:23 ` [PATCH v2 2/4] dt-bindings: regulator: mt6397: Document valid modes Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 6:23 ` [PATCH v2 3/4] regulator: mt6397: Implement of_map_mode Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 6:23 ` [PATCH v2 4/4] arm64: dts: mediatek: Update allowed mt6397 regulator modes for elm boards Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 6:23 ` Anand K Mistry
2020-07-02 15:46 ` [PATCH v2 0/4] regulator: mt6397: Implement of_map_mode regulator_desc function Mark Brown
2020-07-02 15:46 ` Mark Brown
2020-07-02 15:46 ` 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=20200702162231.v2.2.I0a814b246cfe47f8dd1e25553ee881cbcfd0d8eb@changeid \
--to=amistry@google.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=hsin-hsiung.wang@mediatek.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.