linux-kernel - Re: "coupled" regulator support

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: <20160715125039.GI30372@sirena.org.uk>
Date:	Fri, 15 Jul 2016 13:50:39 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Jisheng Zhang <jszhang@...vell.com>
Cc:	Liam Girdwood <lgirdwood@...il.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: "coupled" regulator support

On Fri, Jul 15, 2016 at 08:01:13PM +0800, Jisheng Zhang wrote:

> regR can only be set to v1 if devA and devB all call for set voltage to v1
> regR can set to v2 if devA or devB call for set voltage to v2

> To support this situation, I'd like to add flag to regulator structure and
> patch regulator_check_consumers() to check whether we are safe to set the vol

Surely this is just what normal set voltage calls do?  If devA says
set_voltage(v1, v2) but devB still has set_voltage(v2, v2) then we will
leave the voltage at v2, we'll only allow it to be set to v1 if both
consumers agree that this is a valid voltage.  It feels like there's
something else going on here that I'm missing?

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