From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [PATCH 5/5] regulator: arizona-ldo1: Implement GPIO enable support
Date: Wed, 27 Jun 2012 15:12:06 +0100 [thread overview]
Message-ID: <1340806326-30525-5-git-send-email-broonie@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1340806326-30525-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
---
drivers/regulator/arizona-ldo1.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index 51f02ca..c8f95c0 100644
--- a/drivers/regulator/arizona-ldo1.c
+++ b/drivers/regulator/arizona-ldo1.c
@@ -57,6 +57,9 @@ static const struct regulator_desc arizona_ldo1 = {
};
static const struct regulator_init_data arizona_ldo1_default = {
+ .constraints = {
+ .valid_ops_mask = REGULATOR_CHANGE_STATUS,
+ },
.num_consumer_supplies = 1,
};
@@ -88,6 +91,7 @@ static __devinit int arizona_ldo1_probe(struct platform_device *pdev)
config.dev = arizona->dev;
config.driver_data = ldo1;
config.regmap = arizona->regmap;
+ config.ena_gpio = arizona->pdata.ldoena;
if (arizona->pdata.ldo1)
config.init_data = arizona->pdata.ldo1;
--
1.7.10
prev parent reply other threads:[~2012-06-27 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 14:12 [PATCH 1/5] regulator: core: Factor out enable and disable operations some more Mark Brown
2012-06-27 14:12 ` [PATCH 2/5] regulator: core: Add core support for GPIO controlled enable lines Mark Brown
2012-06-27 14:12 ` [PATCH 3/5] regulator: fixed: Use core GPIO enable support Mark Brown
2012-06-27 14:12 ` [PATCH 4/5] regulator: wm8994: " Mark Brown
2012-06-27 14:12 ` Mark Brown [this message]
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=1340806326-30525-5-git-send-email-broonie@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®