linux-kernel - Re: Removal of regulator-boot-on/always-on when a consumer exists

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: <20160926164903.x6jmpqz3yz646ar7@sirena.org.uk>
Date:   Mon, 26 Sep 2016 09:49:03 -0700
From:   Mark Brown <broonie@...nel.org>
To:     Fabio Estevam <festevam@...il.com>
Cc:     Michael Trimarchi <michael@...rulasolutions.com>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Removal of regulator-boot-on/always-on when a consumer exists

On Mon, Sep 26, 2016 at 01:43:28PM -0300, Fabio Estevam wrote:
> On Mon, Sep 26, 2016 at 1:34 PM, Mark Brown <broonie@...nel.org> wrote:

> > It really depends on what the actual board constraints are - are there
> > other consumers that aren't visible to software, is it electrically safe
> > to power down the rail?

> The can1 node is the only consumer of this regulator.

> The reg_3p3v regulator models a discrete 3.3V power supply with no
> software intervention.

So if it's electrically safe it's electrically safe...

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