From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jeffrey Carlyle <jeff.carlyle@motorola.com>,
Lun Chang <L.chang@motorola.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] regulator: avoid deadlock when disabling regulator with supply
Date: Sun, 10 Oct 2010 11:14:47 +0100 [thread overview]
Message-ID: <1286705687.3429.1.camel@odin> (raw)
In-Reply-To: <20101008211042.GC6098@opensource.wolfsonmicro.com>
On Fri, 2010-10-08 at 14:10 -0700, Mark Brown wrote:
> On Fri, Oct 08, 2010 at 02:49:19PM -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.
> >
> > When I call regulator_disable(A), I end up with a call chain like this:
>
> Looks good!
>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Applied.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-10-10 10:14 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
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 [this message]
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=1286705687.3429.1.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=L.chang@motorola.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jeff.carlyle@motorola.com \
--cc=linux-kernel@vger.kernel.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 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.