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: <CAOMZO5CPF7XLQihx_g4VcBzP=FVeuZ+gCY=t6N_NoUzLHgmb8A@mail.gmail.com>
Date:   Mon, 26 Sep 2016 13:43:28 -0300
From:   Fabio Estevam <festevam@...il.com>
To:     Mark Brown <broonie@...nel.org>
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

Hi Mark,

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.

Thanks