From: Chen Feng <puck.chen@hisilicon.com>
To: <lgirdwood@gmail.com>, <broonie@kernel.org>,
<linux-kernel@vger.kernel.org>, <lee.jones@linaro.org>,
<puck.chen@hisilicon.com>, <w.f@huawei.com>,
<kong.kongxinwei@hisilicon.com>, <haojian.zhuang@linaro.org>
Cc: <suzhuangluan@hisilicon.com>, <dan.zhao@hisilicon.com>
Subject: [PATCH v8 2/5] regulator: hi655x: Document for hi655x regulator
Date: Sun, 14 Feb 2016 14:29:20 +0800 [thread overview]
Message-ID: <1455431363-113771-3-git-send-email-puck.chen@hisilicon.com> (raw)
In-Reply-To: <1455431363-113771-1-git-send-email-puck.chen@hisilicon.com>
This patch adds the device tree binding documentation for
hi655x PMIC regulator.
Signed-off-by: Chen Feng <puck.chen@hisilicon.com>
Signed-off-by: Fei Wang <w.f@huawei.com>
Signed-off-by: Xinwei Kong <kong.kongxinwei@hisilicon.com>
Reviewed-by: Haojian Zhuang <haojian.zhuang@linaro.org>
---
.../regulator/hisilicon,hi655x-regulator.txt | 29 ++++++++++++++++++++++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/hisilicon,hi655x-regulator.txt
diff --git a/Documentation/devicetree/bindings/regulator/hisilicon,hi655x-regulator.txt b/Documentation/devicetree/bindings/regulator/hisilicon,hi655x-regulator.txt
new file mode 100644
index 0000000..14cfdc5
--- /dev/null
+++ b/Documentation/devicetree/bindings/regulator/hisilicon,hi655x-regulator.txt
@@ -0,0 +1,29 @@
+Hisilicon Hi655x Voltage regulators
+
+Note:
+The Hi655x regulator control is managed by Hi655x PMIC.
+So the node of this regulator must be child node of Hi655x
+PMIC node.
+
+The driver uses the regulator core framework, so please also
+take the bindings of regulator.txt for reference.
+
+The valid names for regulators are:
+
+LDO2_2V8 LDO7_SDIO LDO10_2V85 LDO13_1V8 LDO14_2V8
+LDO15_1V8 LDO17_2V5 LDO19_3V0 LDO21_1V8 LDO22_1V2
+
+Example:
+ pmic: pmic@f8000000 {
+ compatible = "hisilicon,hi655x-pmic";
+ ...
+ regulators {
+ ldo2: LDO2@a21 {
+ regulator-name = "LDO2_2V8";
+ regulator-min-microvolt = <2500000>;
+ regulator-max-microvolt = <3200000>;
+ regulator-enable-ramp-delay = <120>;
+ };
+ ...
+ }
+ }
--
1.9.1
next prev parent reply other threads:[~2016-02-14 6:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 6:29 [PATCH v8 0/5] Add Support for Hi6220 PMIC Hi6553 MFD Core Chen Feng
2016-02-14 6:29 ` [PATCH v8 1/5] mfd: hi655x: Add document for mfd hi665x PMIC Chen Feng
2016-02-15 8:32 ` Lee Jones
2016-02-16 1:21 ` Chen Feng
2016-02-27 8:36 ` Wei Xu
2016-04-11 10:40 ` Lee Jones
2016-02-14 6:29 ` Chen Feng [this message]
2016-02-14 6:29 ` [PATCH v8 3/5] mfd: hi655x: Add MFD driver for hi655x Chen Feng
2016-04-11 10:41 ` Lee Jones
[not found] ` <570D982C.6090307@hisilicon.com>
2016-04-19 3:25 ` Guodong Xu
2016-04-19 6:53 ` Lee Jones
2016-04-19 6:57 ` Guodong Xu
2016-05-18 3:14 ` Guodong Xu
2016-02-14 6:29 ` [PATCH v8 4/5] regulator: hi655x: enable regulator for hi655x PMIC Chen Feng
2016-02-14 6:29 ` [PATCH v8 5/5] arm64: dts: hisilicon: Add hi655x pmic dts node Chen Feng
2016-04-11 8:14 ` [PATCH v8 0/5] Add Support for Hi6220 PMIC Hi6553 MFD Core Lee Jones
2016-04-11 8:41 ` Chen Feng
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=1455431363-113771-3-git-send-email-puck.chen@hisilicon.com \
--to=puck.chen@hisilicon.com \
--cc=broonie@kernel.org \
--cc=dan.zhao@hisilicon.com \
--cc=haojian.zhuang@linaro.org \
--cc=kong.kongxinwei@hisilicon.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suzhuangluan@hisilicon.com \
--cc=w.f@huawei.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).