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: <CAOf5uw=ZqA=6PDSpijreWUwEHJ7RYUtROgUZz=6o-5NAZPdAVA@mail.gmail.com>
Date:   Mon, 26 Sep 2016 18:52:10 +0200
From:   Michael Trimarchi <michael@...rulasolutions.com>
To:     Fabio Estevam <festevam@...il.com>
Cc:     Mark Brown <broonie@...nel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Removal of regulator-boot-on/always-on when a consumer exists

Hi

On Mon, Sep 26, 2016 at 6:50 PM, Fabio Estevam <festevam@...il.com> wrote:
> On Mon, Sep 26, 2016 at 1:49 PM, Mark Brown <broonie@...nel.org> wrote:
>
>>> 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...
>
> So regulator-boot-on and  regulator-always-on can go away then?

regulator-always-on and regulator-boot-on just describe them and I don't see
any advantage to remove them

Michael