linux-kernel - Re: Regulator: drivers that need to know their supply

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: <20160407170249.GV1924@sirena.org.uk>
Date:	Thu, 7 Apr 2016 10:02:49 -0700
From:	Mark Brown <broonie@...nel.org>
To:	Martin Fuzzey <mfuzzey@...keon.com>
Cc:	Javier Martinez Canillas <javier@....samsung.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Regulator: drivers that need to know their supply

On Thu, Apr 07, 2016 at 03:25:09PM +0200, Martin Fuzzey wrote:

> To implement the .enable_time() method I need the voltage (which is
> the supply's voltage).

No, this is not sensible.  You should be telling the framework about the
slew rate and letting the framework work out how long it's going to take
to transition.  Your driver shouldn't be peering around inside other
regulators, it should be telling the framework what it does itself and
any handling of interrelationships should be in the framework.

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