From: Liam Girdwood <lrg@kernel.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] regulator: Do bulk enables of regulators in parallel
Date: Mon, 04 Jul 2011 18:53:34 +0100 [thread overview]
Message-ID: <1309802014.3272.16.camel@odin> (raw)
In-Reply-To: <1306195960-5897-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Tue, 2011-05-24 at 08:12 +0800, Mark Brown wrote:
> In order to reduce the impact of ramp times rather than enabling the
> regulators for a device in series use async tasks to run the actual
> enables. This means that the delays which the enables implement can all
> run in parallel, though it does mean that the order in which the
> supplies come on may be unstable.
>
> For super bonus fun points if any of the regulators are shared between
> multiple supplies on the same device (as is rather likely) then this
> will test our locking. Note that in this case we only delay once for
> each physical regulator so the threads shouldn't block each other while
> delaying.
>
> It'd be even nicer if we could coalesce writes to a shared enable registers
> in PMICs but that's definitely future work, and it may also be useful
> and is certainly more achievable to optimise out the parallelism if none
> of the regulators implement ramp delays.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>
> Targetted at 2.6.41 obviously.
>
Applied.
Thanks
Liam
prev parent reply other threads:[~2011-07-04 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 0:12 [PATCH] regulator: Do bulk enables of regulators in parallel Mark Brown
2011-05-24 10:07 ` Liam Girdwood
2011-07-04 17:53 ` Liam Girdwood [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=1309802014.3272.16.camel@odin \
--to=lrg@kernel.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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 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.