linux-kernel - Re: [PATCH] regulator: core: export function to check if regulator always on

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141112113541.GD3815@sirena.org.uk>
Date:	Wed, 12 Nov 2014 11:35:41 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>
Cc:	lgirdwood@...il.com, linux-kernel@...r.kernel.org,
	patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH] regulator: core: export function to check if regulator
 always on

On Wed, Nov 12, 2014 at 11:18:35AM +0000, Richard Fitzgerald wrote:
> Export a function to allow a consumer to check if its supply
> regulator is always on. Drivers might wish to take different
> action based on this - for example skipping time-consuming
> power-saving preparations that are irrelevant if the regulator
> cannot be disabled.

I'd like to see a user here, and I'd also like to understand why this is
a better approach than using a callback to postpone these expensive
operations until the regulator is actually powered off like we already
do for some things like register cache resyncs.  That is normally better
since it also avoids the work in cases where the regulator isn't always
on like reenabling during a delayed powerdown or shared regulators.

You're also missing a !CONFIG_REGULATOR stub.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)