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: <20160926165728.r7kv5rhv4hfntfs5@sirena.org.uk>
Date:   Mon, 26 Sep 2016 09:57:28 -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:50:37PM -0300, Fabio Estevam wrote:

> So regulator-boot-on and  regulator-always-on can go away then?

Like I say I can't give you a definitive answer on this without looking
at the actual hardware and what it needs.  Based on what you're saying
it sounds like it won't be an issue from the point of view of disrupting
other users but without knowing the hardware I can't tell if the
connected device can safely have power removed, sometimes devices don't
like having only one of many supplies removed.

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