From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jeffrey Carlyle <jeff.carlyle@motorola.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
Lun Chang <L.chang@motorola.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: avoid deadlock when disabling regulator with supply
Date: Fri, 8 Oct 2010 11:57:40 -0700 [thread overview]
Message-ID: <20101008185739.GA6098@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1286563435-31239-1-git-send-email-jeff.carlyle@motorola.com>
On Fri, Oct 08, 2010 at 01:43:54PM -0500, Jeffrey Carlyle wrote:
> I have a regulator A that sets regulator B as its supply. When I call
> set_supply to add B as the supply for A, regulator A gets added to the
> supply_list for regulator B.
Looks good, thanks!
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
but some stylistic things below:
> Change-Id: I769669452b9e1b59b252298d589738aabb03529c
Hrm?
> static int _regulator_get_voltage(struct regulator_dev *rdev);
> static int _regulator_get_current_limit(struct regulator_dev *rdev);
> static unsigned int _regulator_get_mode(struct regulator_dev *rdev);
> @@ -1343,12 +1344,14 @@ int regulator_enable(struct regulator *regulator)
> mutex_lock(&rdev->mutex);
> ret = _regulator_enable(rdev);
> mutex_unlock(&rdev->mutex);
> +
> return ret;
> }
> EXPORT_SYMBOL_GPL(regulator_enable);
Random indentation change here.
> +
> + if (supply_rdev)
> + regulator_disable(
> + get_device_regulator(rdev_get_dev(supply_rdev))
> + );
> +
Eew, indentation! In cases like this it's better to just ignore the
excesive line length.
next prev parent reply other threads:[~2010-10-08 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 18:16 [PATCH 0/3] Regulator updates for 2.6.34 Mark Brown
2010-01-04 18:17 ` [PATCH 1/3] regulator: Add notifier event on regulator disable Mark Brown
2010-10-08 13:27 ` Jeffrey Carlyle
2010-10-08 16:30 ` Mark Brown
2010-10-08 18:43 ` [PATCH] regulator: avoid deadlock when disabling regulator with supply Jeffrey Carlyle
2010-10-08 18:57 ` Mark Brown [this message]
2010-10-08 19:48 ` [PATCH v2] " y
2010-10-08 19:49 ` Jeffrey Carlyle
2010-10-08 21:10 ` Mark Brown
2010-10-10 10:14 ` Liam Girdwood
2010-01-04 18:17 ` [PATCH 2/3] regulator: Allow regulators to specify the time taken to ramp on enable Mark Brown
2010-01-04 18:17 ` [PATCH 3/3] regulator: Implement enable_time() for WM835x ISINKs Mark Brown
2010-01-04 20:35 ` [PATCH 0/3] Regulator updates for 2.6.34 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=20101008185739.GA6098@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=L.chang@motorola.com \
--cc=jeff.carlyle@motorola.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.