linux-kernel - Re: Ask a question about regulator always_on and 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>] [day] [month] [year] [list]

Date:	Mon, 9 Jul 2012 12:15:57 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	王艇艇 <wtt_usst@....com>
Cc:	linux-kernel@...r.kernel.org, lrg@...mlogic.co.uk
Subject: Re: Ask a question about regulator always_on and boot_on

On Mon, Jul 09, 2012 at 10:29:54AM +0800, 王艇艇 wrote:

> Sorry to bother you.

You appear to be asking exactly the same question as you asked last
week (and this is also the second time you asked today...).
Unsurprisingly the answer is also exactly the same.

> When I set the regulator always_on and boot_on item as 0 at the initial stage.

> The regulator should not enabled, right?

No.  always_on means that the regulator will never be disabled.  boot_on
means that the regulator is expacted to

> Why not add these code for the obvious operation to disable the regulator at initial stage?

The goal is still that the system specifies full constraints which means
that any unused regulators are powered down.

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