From: fabio.baltieri@linaro.org (Fabio Baltieri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: update V-INTCORE constraints
Date: Wed, 27 Mar 2013 16:21:34 +0100 [thread overview]
Message-ID: <1364397694-14126-1-git-send-email-fabio.baltieri@linaro.org> (raw)
Update V-INTCORE regulator constraints to allow voltage and
configuration changes from consumer drivers.
Signed-off-by: Fabio Baltieri <fabio.baltieri@linaro.org>
---
Hi Linus,
this patch adds the regulators bits I'm missing for ux500-musb patches.
Without this I just get a runtime warning like:
V-INTCORE: operation not allowed
but the driver works anyway and there are no build dependencies, so I
think this can safely go in the arm-soc tree on its own, and the whole
thing should work happily in -next.
Thanks,
Fabio
arch/arm/mach-ux500/board-mop500-regulators.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-ux500/board-mop500-regulators.c b/arch/arm/mach-ux500/board-mop500-regulators.c
index 2a17bc5..0a428db 100644
--- a/arch/arm/mach-ux500/board-mop500-regulators.c
+++ b/arch/arm/mach-ux500/board-mop500-regulators.c
@@ -392,7 +392,15 @@ struct regulator_init_data ab8500_regulators[AB8500_NUM_REGULATORS] = {
[AB8500_LDO_INTCORE] = {
.constraints = {
.name = "V-INTCORE",
- .valid_ops_mask = REGULATOR_CHANGE_STATUS,
+ .min_uV = 1250000,
+ .max_uV = 1350000,
+ .input_uV = 1800000,
+ .valid_ops_mask = REGULATOR_CHANGE_VOLTAGE |
+ REGULATOR_CHANGE_STATUS |
+ REGULATOR_CHANGE_MODE |
+ REGULATOR_CHANGE_DRMS,
+ .valid_modes_mask = REGULATOR_MODE_NORMAL |
+ REGULATOR_MODE_IDLE,
},
.num_consumer_supplies = ARRAY_SIZE(ab8500_vintcore_consumers),
.consumer_supplies = ab8500_vintcore_consumers,
--
1.8.1.3
next reply other threads:[~2013-03-27 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:21 Fabio Baltieri [this message]
2013-04-02 8:26 ` [PATCH] ARM: ux500: update V-INTCORE constraints Linus Walleij
2013-04-02 8:38 ` Mark Brown
2013-04-02 8:44 ` Fabio Baltieri
2013-04-02 8:46 ` Mark Brown
2013-04-02 8:51 ` [PATCH RESEND] " Fabio Baltieri
2013-04-02 9:23 ` Lee Jones
2013-04-02 9:34 ` Fabio Baltieri
2013-04-02 9:24 ` [PATCH] " Lee Jones
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=1364397694-14126-1-git-send-email-fabio.baltieri@linaro.org \
--to=fabio.baltieri@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).