From: dahuang@nvidia.com
To: lrg@ti.com, broonie@opensource.wolfsonmicro.com,
mike@compulab.co.il, sameo@linux.intel.com, xxie@nvidia.com,
gking@nvidia.com
Cc: linux-kernel@vger.kernel.org, Danny Huang <dahuang@nvidia.com>
Subject: [PATCH] regulator: tps6586x: add SMx slew rate setting
Date: Thu, 4 Aug 2011 19:34:22 +0800 [thread overview]
Message-ID: <1312457662-4490-1-git-send-email-dahuang@nvidia.com> (raw)
From: Danny Huang <dahuang@nvidia.com>
Add output vlotage slew rate setting for SM0/SM1
From: Xin Xie <xxie@nvidia.com>
Signed-off-by: Xin Xie <xxie@nvidia.com>
Signed-off-by: Danny Huang <dahuang@nvidia.com>
---
drivers/regulator/tps6586x-regulator.c | 27 ++++++++++++++++++++++++++-
include/linux/mfd/tps6586x.h | 15 +++++++++++++++
2 files changed, 41 insertions(+), 1 deletions(-)
diff --git a/drivers/regulator/tps6586x-regulator.c b/drivers/regulator/tps6586x-regulator.c
index bb04a75..9e5b459 100644
--- a/drivers/regulator/tps6586x-regulator.c
+++ b/drivers/regulator/tps6586x-regulator.c
@@ -332,6 +332,31 @@ static inline int tps6586x_regulator_preinit(struct device *parent,
1 << ri->enable_bit[1]);
}
+static int tps6586x_regulator_set_slew_rate(struct platform_device *pdev)
+{
+ struct device *parent = pdev->dev.parent;
+ struct regulator_init_data *p = pdev->dev.platform_data;
+ struct tps6586x_settings *setting = p->driver_data;
+ uint8_t reg;
+
+ if (setting == NULL)
+ return 0;
+
+ /* only SM0 and SM1 can have the slew rate settings */
+ switch (pdev->id) {
+ case TPS6586X_ID_SM_0:
+ reg = TPS6586X_SM0SL;
+ break;
+ case TPS6586X_ID_SM_1:
+ reg = TPS6586X_SM1SL;
+ break;
+ default:
+ dev_err(&pdev->dev, "invalid regulator ID\n");
+ return -EINVAL;
+ }
+ return tps6586x_write(parent, reg, setting->slew_rate);
+}
+
static inline struct tps6586x_regulator *find_regulator_info(int id)
{
struct tps6586x_regulator *ri;
@@ -374,7 +399,7 @@ static int __devinit tps6586x_regulator_probe(struct platform_device *pdev)
platform_set_drvdata(pdev, rdev);
- return 0;
+ return tps6586x_regulator_set_slew_rate(pdev);
}
static int __devexit tps6586x_regulator_remove(struct platform_device *pdev)
diff --git a/include/linux/mfd/tps6586x.h b/include/linux/mfd/tps6586x.h
index b6bab1b..9dfb2bb 100644
--- a/include/linux/mfd/tps6586x.h
+++ b/include/linux/mfd/tps6586x.h
@@ -48,6 +48,21 @@ enum {
TPS6586X_INT_RTC_ALM2,
};
+enum {
+ TPS6586x_SLEW_RATE_INSTANTLY,
+ TPS6586x_SLEW_RATE_110UV,
+ TPS6586x_SLEW_RATE_220UV,
+ TPS6586x_SLEW_RATE_440UV,
+ TPS6586x_SLEW_RATE_880UV,
+ TPS6586x_SLEW_RATE_1760UV,
+ TPS6586x_SLEW_RATE_3520UV,
+ TPS6586x_SLEW_RATE_7040UV,
+};
+
+struct tps6586x_settings {
+ int slew_rate;
+};
+
struct tps6586x_subdev_info {
int id;
const char *name;
--
1.7.0.4
next reply other threads:[~2011-08-04 11:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 11:34 dahuang [this message]
2011-08-04 12:12 ` Mark Brown
2011-08-05 11:51 ` Danny Huang
2011-08-08 9:37 ` Mark Brown
2011-08-08 12:28 ` Danny Huang
2011-08-08 13:32 ` Mark Brown
2011-08-04 12:42 ` Mark Brown
2011-08-05 11:53 ` Danny Huang
2011-08-09 10:47 dahuang
2011-08-09 16:06 ` Mark Brown
2011-08-22 9:35 ` Samuel Ortiz
2011-08-22 9:41 ` Liam Girdwood
2011-08-28 16:49 ` Liam Girdwood
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=1312457662-4490-1-git-send-email-dahuang@nvidia.com \
--to=dahuang@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gking@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=mike@compulab.co.il \
--cc=sameo@linux.intel.com \
--cc=xxie@nvidia.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
Powered by JetHome