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-next>] [day] [month] [year] [list]
Message-ID: <20160715200113.0f3cd823@xhacker>
Date:	Fri, 15 Jul 2016 20:01:13 +0800
From:	Jisheng Zhang <jszhang@...vell.com>
To:	Mark Brown <broonie@...nel.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	<linux-arm-kernel@...ts.infradead.org>
CC:	<linux-kernel@...r.kernel.org>
Subject: "coupled" regulator support

Hi,

I dunno how to name this kind of regulator, my situation is:

multiple devices connects to one voltage regulator_dev, e.g devA and devB connects
to regR, regR only support two voltage v1 and v2, let's say v1 < v2

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

Is this patch acceptable or we already have elegant solution?

Thanks in advance,
Jisheng

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ