From: Henry Chen <henryc.chen@mediatek.com>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Henry Chen <henryc.chen@mediatek.com>
Subject: [PATCH v2 1/3] regulator: DT: Add DT property for operation mode configuration
Date: Mon, 23 May 2016 15:13:29 +0800 [thread overview]
Message-ID: <1463987611-32139-2-git-send-email-henryc.chen@mediatek.com> (raw)
In-Reply-To: <1463987611-32139-1-git-send-email-henryc.chen@mediatek.com>
Some regulators support their operating mode to be changed by consumers for
module specific purpose. Add a DT property to support this.
Signed-off-by: Henry Chen <henryc.chen@mediatek.com>
---
Documentation/devicetree/bindings/regulator/regulator.txt | 5 +++++
include/dt-bindings/regulator/regulator.h | 14 ++++++++++++++
2 files changed, 19 insertions(+)
create mode 100644 include/dt-bindings/regulator/regulator.h
diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt
index ecfc593..e505d0b 100644
--- a/Documentation/devicetree/bindings/regulator/regulator.txt
+++ b/Documentation/devicetree/bindings/regulator/regulator.txt
@@ -49,6 +49,11 @@ Optional properties:
0: Disable active discharge.
1: Enable active discharge.
Absence of this property will leave configuration to default.
+- regulator-supported-modes: Regulators can run in a variety of different
+ operating modes depending on output load. This allows further system power
+ savings by selecting the best (and most efficient) regulator mode for a
+ desired load. The definition for each of these operation is defined at
+ include/dt-bindings/regulator/regulator.h
Deprecated properties:
- regulator-compatible: If a regulator chip contains multiple
diff --git a/include/dt-bindings/regulator/regulator.h b/include/dt-bindings/regulator/regulator.h
new file mode 100644
index 0000000..2ed1dfd
--- /dev/null
+++ b/include/dt-bindings/regulator/regulator.h
@@ -0,0 +1,14 @@
+/*
+ * This header provides constants for binding regulator.
+ */
+
+#ifndef _DT_BINDINGS_REGULATOR_REGULATOR_H
+#define _DT_BINDINGS_REGULATOR_REGULATOR_H
+
+/* Regulator operating modes */
+#define REGULATOR_OPERATION_MODE_FAST 0x0
+#define REGULATOR_OPERATION_MODE_NORMAL 0x1
+#define REGULATOR_OPERATION_MODE_IDLE 0x2
+#define REGULATOR_OPERATION_MODE_STANDBY 0x3
+
+#endif
--
1.8.1.1.dirty
next prev parent reply other threads:[~2016-05-23 7:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 7:13 Add support for regulator operation mode of mt6397 Henry Chen
2016-05-23 7:13 ` Henry Chen [this message]
2016-05-23 10:47 ` [PATCH v2 1/3] regulator: DT: Add DT property for operation mode configuration Mark Rutland
2016-05-23 11:28 ` Mark Brown
2016-05-31 8:20 ` Fan Chen
2016-06-03 0:16 ` Mark Brown
[not found] ` <20160603001600.GX2282-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-03 5:42 ` Fan Chen
[not found] ` <1463987611-32139-1-git-send-email-henryc.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2016-05-23 7:13 ` [PATCH v2 2/3] regulator: of: Add support for parsing operation mode Henry Chen
2016-05-23 7:13 ` [PATCH v2 3/3] regulator: mt6397: Add buck change mode regulator interface for mt6397 Henry Chen
2016-05-23 11:29 ` Mark Brown
2016-05-23 17:50 ` Applied "regulator: mt6397: Add buck change mode regulator interface for mt6397" to the regulator tree 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=1463987611-32139-2-git-send-email-henryc.chen@mediatek.com \
--to=henryc.chen@mediatek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=pawel.moll@arm.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).