From: Keerthy <j-keerthy@ti.com>
To: lee.jones@linaro.org, robh+dt@kernel.org, broonie@kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, t-kristo@ti.com, j-keerthy@ti.com
Subject: [PATCH 3/3] regulator: lp87565: Add 4-phase lp87561 regulator support
Date: Wed, 15 May 2019 15:38:48 +0530 [thread overview]
Message-ID: <20190515100848.19560-4-j-keerthy@ti.com> (raw)
In-Reply-To: <20190515100848.19560-1-j-keerthy@ti.com>
The LP8756x family has a single output 4-phase regulator
configuration. Add support for the same. The control
lies in the master buck which is buck0 for 4-phase
configuration. Enable/disable/voltage set happen via
buck0 registers.
Data Sheet: https://www.ti.com/lit/ds/symlink/lp87561-q1.pdf
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
drivers/regulator/lp87565-regulator.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/regulator/lp87565-regulator.c b/drivers/regulator/lp87565-regulator.c
index 81eb4b890c0c..8255650df1cd 100644
--- a/drivers/regulator/lp87565-regulator.c
+++ b/drivers/regulator/lp87565-regulator.c
@@ -153,6 +153,12 @@ static const struct lp87565_regulator regulators[] = {
LP87565_REG_BUCK2_CTRL_1,
LP87565_BUCK_CTRL_1_EN, 3230,
buck0_1_2_3_ranges, LP87565_REG_BUCK2_CTRL_2),
+ LP87565_REGULATOR("BUCK3210", LP87565_BUCK_3210, "buck3210",
+ lp87565_buck_ops, 256, LP87565_REG_BUCK0_VOUT,
+ LP87565_BUCK_VSET, LP87565_REG_BUCK0_CTRL_1,
+ LP87565_BUCK_CTRL_1_EN |
+ LP87565_BUCK_CTRL_1_FPWM_MP_0_2, 3230,
+ buck0_1_2_3_ranges, LP87565_REG_BUCK0_CTRL_2),
};
static int lp87565_regulator_probe(struct platform_device *pdev)
@@ -172,6 +178,9 @@ static int lp87565_regulator_probe(struct platform_device *pdev)
if (lp87565->dev_type == LP87565_DEVICE_TYPE_LP87565_Q1) {
min_idx = LP87565_BUCK_10;
max_idx = LP87565_BUCK_23;
+ } else if (lp87565->dev_type == LP87565_DEVICE_TYPE_LP87561_Q1) {
+ min_idx = LP87565_BUCK_3210;
+ max_idx = LP87565_BUCK_3210;
}
for (i = min_idx; i <= max_idx; i++) {
--
2.17.1
next prev parent reply other threads:[~2019-05-15 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 10:08 [PATCH 0/3] mfd: lp87565: Add support for 4-phase lp87561 combination Keerthy
2019-05-15 10:08 ` [PATCH 1/3] dt-bindings: mfd: lp87565: Add lp87561 configuration Keerthy
2019-06-03 9:03 ` Lee Jones
2019-05-15 10:08 ` [PATCH 2/3] mfd: lp87565: Add support for 4-phase lp87561 combination Keerthy
2019-06-03 9:03 ` Lee Jones
2019-05-15 10:08 ` Keerthy [this message]
2019-05-15 11:08 ` [PATCH 3/3] regulator: lp87565: Add 4-phase lp87561 regulator support Mark Brown
2019-05-15 11:13 ` Keerthy
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=20190515100848.19560-4-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.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).