linux-kernel - Re: [PATCH] regulator: core: Keep boot

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: <20120423110522.GB8318@opensource.wolfsonmicro.com>
Date:	Mon, 23 Apr 2012 12:05:22 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Ulf Hansson <ulf.hansson@...ricsson.com>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Mattias WALLIN <mattias.wallin@...ricsson.com>,
	Jonas ABERG <jonas.aberg@...ricsson.com>,
	Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH] regulator: core: Keep boot_on regulators powered during
 init

On Mon, Apr 23, 2012 at 12:52:05PM +0200, Ulf Hansson wrote:

> I realize that using boot_on, which has been around for quite some
> time could have problems.  If not using the existing boot_on
> constraint, do you have an idea of how to accomplish what I want?
> Should I invent a new constraint option to be used in
> regulator_init_complete!?

To be honest I don't entirely understand what your goal is at the system
level - the current idea is that either the regulator will be marked as
always_on or it should be enabled by a consumer.  What is the scenario
in which neither of these is sufficient?

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