linux-kernel - Re: RFC: Regulator Framework Voltage Setting

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: <20100602100718.GB13983@rakim.wolfsonmicro.main>
Date:	Wed, 2 Jun 2010 11:07:18 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Linus WALLEIJ <linus.walleij@...ricsson.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Bengt JONSSON <bengt.g.jonsson@...ricsson.com>,
	Sundar R IYER <sundar.iyer@...ricsson.com>
Subject: Re: RFC: Regulator Framework Voltage Setting

On Wed, Jun 02, 2010 at 11:18:00AM +0200, Linus WALLEIJ wrote:

> Our questions:
> - Is this the correct interpretation of the current functionality?
> - Is the proposed behaviour what you would expect?
> - Any other problems to consider?

The current expectation is that a consumer that really needs a voltage
setting will have exclusive use of the regulator and won't share it with
other consumers.  There was some support for combining constraints from
multiple consumers originally but it got removed due to requests from
David Brownell (there's not actually much demand for this feature
anyway, finding devices which support but do not required DVS is
actually quite hard and generally the power requirments for shared rails
get fixed at hardware build tiem).
--
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/