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 1/4] regulator: mt6397: Move buck modes into header file
Date: Thu, 2 Jul 2020 16:23:17 +1000 [thread overview]
Message-ID: <20200702162231.v2.1.Icf69e2041b1af4548347018186c3ba6310f53e66@changeid> (raw)
In-Reply-To: <20200702062320.2903147-1-amistry@google.com>
This will allow device trees to make use of these constants.
Signed-off-by: Anand K Mistry <amistry@google.com>
---
Changes in v2: None
drivers/regulator/mt6397-regulator.c | 4 +---
.../regulator/mediatek,mt6397-regulator.h | 15 +++++++++++++++
2 files changed, 16 insertions(+), 3 deletions(-)
create mode 100644 include/dt-bindings/regulator/mediatek,mt6397-regulator.h
diff --git a/drivers/regulator/mt6397-regulator.c b/drivers/regulator/mt6397-regulator.c
index 269c2a6028e8..d51e98ce1138 100644
--- a/drivers/regulator/mt6397-regulator.c
+++ b/drivers/regulator/mt6397-regulator.c
@@ -13,9 +13,7 @@
#include <linux/regulator/machine.h>
#include <linux/regulator/mt6397-regulator.h>
#include <linux/regulator/of_regulator.h>
-
-#define MT6397_BUCK_MODE_AUTO 0
-#define MT6397_BUCK_MODE_FORCE_PWM 1
+#include <dt-bindings/regulator/mediatek,mt6397-regulator.h>
/*
* MT6397 regulators' information
diff --git a/include/dt-bindings/regulator/mediatek,mt6397-regulator.h b/include/dt-bindings/regulator/mediatek,mt6397-regulator.h
new file mode 100644
index 000000000000..99869a8665cf
--- /dev/null
+++ b/include/dt-bindings/regulator/mediatek,mt6397-regulator.h
@@ -0,0 +1,15 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+
+#ifndef _DT_BINDINGS_REGULATOR_MEDIATEK_MT6397_H_
+#define _DT_BINDINGS_REGULATOR_MEDIATEK_MT6397_H_
+
+/*
+ * Buck mode constants which may be used in devicetree properties (eg.
+ * regulator-initial-mode, regulator-allowed-modes).
+ * See the manufacturer's datasheet for more information on these modes.
+ */
+
+#define MT6397_BUCK_MODE_AUTO 0
+#define MT6397_BUCK_MODE_FORCE_PWM 1
+
+#endif
--
2.27.0.212.ge8ba1cc988-goog
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-07-02 6:23 UTC|newest]
Thread overview: 6+ 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 [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 ` [PATCH v2 3/4] regulator: mt6397: Implement of_map_mode 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 15:46 ` [PATCH v2 0/4] regulator: mt6397: Implement of_map_mode regulator_desc function 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.1.Icf69e2041b1af4548347018186c3ba6310f53e66@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 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).