linux-kernel - Re: [PATCH V2 1/5] bindings: regulator: added support for suspend states

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: <CAG2=9p-ec1oVe-+O0TGYFF-E5dGrP3FoRZXb1sCyjNScVvGNQg@mail.gmail.com>
Date:   Mon, 8 Jan 2018 14:36:36 +0800
From:   Chunyan Zhang <zhang.chunyan@...aro.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Rob Herring <robh@...nel.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Ulf Hansson <ulf.hansson@...aro.org>,
        Chunyan Zhang <zhang.lyra@...il.com>
Subject: Re: [PATCH V2 1/5] bindings: regulator: added support for suspend states

On 6 January 2018 at 03:18, Mark Brown <broonie@...nel.org> wrote:
> On Fri, Jan 05, 2018 at 12:53:28PM -0600, Rob Herring wrote:
>> On Thu, Jan 04, 2018 at 03:22:44PM +0800, Chunyan Zhang wrote:
>
>> > +   - regulator-suspend-microvolt: the default voltage which regulator
>> > +     would be set in suspend. The voltage for suspend also can be
>> > +     adjusted among {regulator-suspend-min-microvolt,
>> > +     regulator-suspend-max-microvolt} by calling
>> > +     regulator_set_suspend_voltage(). This property is not deprecated,
>
>> You mean "is deprecated", right?

Ah, right, will correct this.

>
> I suspect "is now" but yeah.
>
>> > +   - regulator-changeable-in-suspend: whether the default voltage and
>> > +     the regulator on/off in suspend can be changed in runtime.
>
>> Is this not implied by having the constraints? Or the driver should know
>> this. The simply means you have some 2nd bank of registers for settings
>> while in suspend mode, right?
>
> No, it means that the software has permission to use those changes to
> those registers - we only want to be changing things if the user has
> permission to change them since some systems will have specific
> constraints, we don't know if it's safe without being explicitly told.
> You're right that we could infer this from a range being provided
> though, let's do that.

Ok, so we don't need this property IIUC, and instead we just need to check
if the regulator-suspend-min-microvolt and regulator-suspend-max-microvolt
are set to the same value, right?

Thanks,
Chunyan