From: Balaji T K <balajitk@ti.com>
To: linux-omap@vger.kernel.org, lrg@slimlogic.co.uk
Cc: broonie@opensource.wolfsonmicro.com, lrg@ti.com,
gg@slimlogic.co.uk, Balaji T K <balajitk@ti.com>
Subject: [PATCH 1/2] regulator: twl6030: do not write to _GRP for regulator enable
Date: Fri, 20 May 2011 19:03:51 +0530 [thread overview]
Message-ID: <1305898432-14939-2-git-send-email-balajitk@ti.com> (raw)
In-Reply-To: <1305898432-14939-1-git-send-email-balajitk@ti.com>
TWL6030: regulator is enabled via VREG_STATE
TWL4030: regulator is enabled via VREG_GRP
Since there is nothing common, split twlreg_enable similar to other regulator_ops
Signed-off-by: Balaji T K <balajitk@ti.com>
---
drivers/regulator/twl-regulator.c | 39 +++++++++++++++++++++++-------------
1 files changed, 25 insertions(+), 14 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c b/drivers/regulator/twl-regulator.c
index 2a808c2..abb40c6 100644
--- a/drivers/regulator/twl-regulator.c
+++ b/drivers/regulator/twl-regulator.c
@@ -156,7 +156,7 @@ static int twl6030reg_is_enabled(struct regulator_dev *rdev)
return grp && (val == TWL6030_CFG_STATE_ON);
}
-static int twlreg_enable(struct regulator_dev *rdev)
+static int twl4030reg_enable(struct regulator_dev *rdev)
{
struct twlreg_info *info = rdev_get_drvdata(rdev);
int grp;
@@ -166,17 +166,28 @@ static int twlreg_enable(struct regulator_dev *rdev)
if (grp < 0)
return grp;
- if (twl_class_is_4030())
- grp |= P1_GRP_4030;
- else
- grp |= P1_GRP_6030;
+ grp |= P1_GRP_4030;
ret = twlreg_write(info, TWL_MODULE_PM_RECEIVER, VREG_GRP, grp);
- if (!ret && twl_class_is_6030())
- ret = twlreg_write(info, TWL_MODULE_PM_RECEIVER, VREG_STATE,
- grp << TWL6030_CFG_STATE_GRP_SHIFT |
- TWL6030_CFG_STATE_ON);
+ udelay(info->delay);
+
+ return ret;
+}
+
+static int twl6030reg_enable(struct regulator_dev *rdev)
+{
+ struct twlreg_info *info = rdev_get_drvdata(rdev);
+ int grp;
+ int ret;
+
+ grp = twlreg_read(info, TWL_MODULE_PM_RECEIVER, VREG_GRP);
+ if (grp < 0)
+ return grp;
+
+ ret = twlreg_write(info, TWL_MODULE_PM_RECEIVER, VREG_STATE,
+ grp << TWL6030_CFG_STATE_GRP_SHIFT |
+ TWL6030_CFG_STATE_ON);
udelay(info->delay);
@@ -473,7 +484,7 @@ static struct regulator_ops twl4030ldo_ops = {
.set_voltage = twl4030ldo_set_voltage,
.get_voltage = twl4030ldo_get_voltage,
- .enable = twlreg_enable,
+ .enable = twl4030reg_enable,
.disable = twlreg_disable,
.is_enabled = twl4030reg_is_enabled,
@@ -531,7 +542,7 @@ static struct regulator_ops twl6030ldo_ops = {
.set_voltage = twl6030ldo_set_voltage,
.get_voltage = twl6030ldo_get_voltage,
- .enable = twlreg_enable,
+ .enable = twl6030reg_enable,
.disable = twlreg_disable,
.is_enabled = twl6030reg_is_enabled,
@@ -564,7 +575,7 @@ static struct regulator_ops twl4030fixed_ops = {
.get_voltage = twlfixed_get_voltage,
- .enable = twlreg_enable,
+ .enable = twl4030reg_enable,
.disable = twlreg_disable,
.is_enabled = twl4030reg_is_enabled,
@@ -578,7 +589,7 @@ static struct regulator_ops twl6030fixed_ops = {
.get_voltage = twlfixed_get_voltage,
- .enable = twlreg_enable,
+ .enable = twl6030reg_enable,
.disable = twlreg_disable,
.is_enabled = twl6030reg_is_enabled,
@@ -588,7 +599,7 @@ static struct regulator_ops twl6030fixed_ops = {
};
static struct regulator_ops twl6030_fixed_resource = {
- .enable = twlreg_enable,
+ .enable = twl6030reg_enable,
.disable = twlreg_disable,
.is_enabled = twl6030reg_is_enabled,
.get_status = twl6030reg_get_status,
--
1.7.0.4
next prev parent reply other threads:[~2011-05-20 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 13:33 [PATCH 0/2] regulator: twl6030: do not write to _GRP for enable/disable Balaji T K
2011-05-20 13:33 ` Balaji T K [this message]
2011-05-22 6:50 ` [PATCH 1/2] regulator: twl6030: do not write to _GRP for regulator enable Mark Brown
2011-05-22 9:26 ` Liam Girdwood
2011-05-20 13:33 ` [PATCH 2/2] regulator: twl6030: do not write to _GRP for regulator disable Balaji T K
2011-05-22 6:59 ` 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=1305898432-14939-2-git-send-email-balajitk@ti.com \
--to=balajitk@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=lrg@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).