linux-kernel - Re: [PATCH] regulator: core: Optimise enable/disable path for always on regulators

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: <1334860536.4452.0.camel@odin>
Date:	Thu, 19 Apr 2012 19:35:36 +0100
From:	Liam Girdwood <lrg@...com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Jassi Brar <jaswinder.singh@...aro.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: core: Optimise enable/disable path for
 always on regulators

On Thu, 2012-04-19 at 13:30 +0100, Mark Brown wrote:
> If a regulator is always on for any reason then cache that when the
> consumer is created and use it to optimise away the need to take locks
> or recurse up the supply tree when consumers do enable or disable calls.
> The scheduling of asynchronous work for bulk enables is also skipped.
> 
> We don't actually check if the device physically supports control on the
> basis that constraints allowing status changes on physically always on
> regulators are nonsensical anyway.
> 
> This is a very common pattern in hardware - it's normal to have some
> power supplies that have either no software control or are critical to
> system function - so many systems should be able to benefit.
> 
> Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> ---

Acked-by: Liam Girdwood <lrg@...com>

--
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/