linux-kernel - Re: [PATCH] regulator: Do bulk enables of regulators in parallel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1309802014.3272.16.camel@odin>
Date:	Mon, 04 Jul 2011 18:53:34 +0100
From:	Liam Girdwood <lrg@...nel.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH] regulator: Do bulk enables of regulators in parallel

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@...nsource.wolfsonmicro.com>
> ---
> 
> Targetted at 2.6.41 obviously.
> 

Applied.

Thanks

Liam

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/