From: Laxman Dewangan <ldewangan@nvidia.com>
To: <lrg@ti.com>, <broonie@opensource.wolfsonmicro.com>,
<rabin.vincent@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH V2] regulator: disable supply regulator if it is enabled for boot-on
Date: Wed, 29 Aug 2012 20:23:09 +0530 [thread overview]
Message-ID: <1346251989-26537-1-git-send-email-ldewangan@nvidia.com> (raw)
If supply regulator is enabled because of boot-on (not always-on)
then disable regulator need to be call if regulator have some
user or full constraint has been enabled.
This will make sure that reference count of supply regulator
is in sync with child regulator's state.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Reported-by: Rabin Vincent <rabin.vincent@gmail.com>
---
Changes from V1:
Rabin reported that the nested locking trace is getting generated.
This is because the regulator lock mutex and disable himself and then
call for supply disable which again lock the regulator lock.
Probably because both lock is taken from regulator structure in nested
manner, the trace is getting generated.
Rewritten patch to avoid nested locking.
drivers/regulator/core.c | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 06186ba..e54537f 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -3606,6 +3606,7 @@ static int __init regulator_init_complete(void)
* default behaviour in the future.
*/
list_for_each_entry(rdev, ®ulator_list, list) {
+ bool supply_disable = false;
ops = rdev->desc->ops;
c = rdev->constraints;
@@ -3614,8 +3615,11 @@ static int __init regulator_init_complete(void)
mutex_lock(&rdev->mutex);
- if (rdev->use_count)
+ if (rdev->use_count) {
+ if (rdev->supply && c->boot_on)
+ supply_disable = true;
goto unlock;
+ }
/* If we can't read the status assume it's on. */
if (ops->is_enabled)
@@ -3634,6 +3638,8 @@ static int __init regulator_init_complete(void)
if (ret != 0) {
rdev_err(rdev, "couldn't disable: %d\n", ret);
}
+ if (rdev->supply)
+ supply_disable = true;
} else {
/* The intention is that in future we will
* assume that full constraints are provided
@@ -3645,6 +3651,8 @@ static int __init regulator_init_complete(void)
unlock:
mutex_unlock(&rdev->mutex);
+ if (supply_disable)
+ regulator_disable(rdev->supply);
}
mutex_unlock(®ulator_list_mutex);
--
1.7.1.1
next reply other threads:[~2012-08-29 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 14:53 Laxman Dewangan [this message]
2012-08-30 18:24 ` Rabin Vincent
2012-08-30 18:27 ` 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=1346251989-26537-1-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rabin.vincent@gmail.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®