linux-kernel - Re: [PATCH 3/4] regulator: added register initialization for ab8500 regulators

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]

Date:	Thu, 10 Mar 2011 13:50:53 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Linus Walleij <linus.walleij@...ricsson.com>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>, linux-kernel@...r.kernel.org,
	Lee Jones <lee.jones@...aro.org>,
	Bengt Jonsson <bengt.g.jonsson@...ricsson.com>,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH 3/4] regulator: added register initialization for
 ab8500 regulators

On Thu, Mar 10, 2011 at 02:43:51PM +0100, Linus Walleij wrote:
> From: Bengt Jonsson <bengt.g.jonsson@...ricsson.com>
> 
> The regulators can come up in a number of undefined
> states, depending on boot path, firmware revisions and
> things like kexec():ing into a new kernel. Provide a
> platform initialization vector so that we have a known
> state when we have booted the kernel.

This should be done using the regulator constraints, there's nothing
device specific about this.
--
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/