linux-kernel - Re: [RFT PATCH] regulator: core: Require regulator drivers to check uV for get_optimum

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] [day] [month] [year] [list]

Message-ID: <CAD=FV=XZTzwROoVtA+qrpy5rrrM2RH3+tZFR0-KFTu79ea4rig@mail.gmail.com>
Date:   Wed, 24 Aug 2022 14:24:28 -0700
From:   Doug Anderson <dianders@...omium.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Andrew Halaney <ahalaney@...hat.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFT PATCH] regulator: core: Require regulator drivers to check
 uV for get_optimum_mode()

Hi,

On Tue, Aug 23, 2022 at 3:49 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Tue, Aug 23, 2022 at 03:32:44PM -0700, Doug Anderson wrote:
>
> > I guess maybe we could add the "initial mode" as an implicitly allowed
> > mode? I guess the other option is to implicitly disable
> > regulator-allow-set-load if no allowed modes are listed? Both of these
>
> We should do the former, or equivalently just noop out of set_load() via
> set_optimium_mode() if no modes are allowed.

OK, v2 posted where I kept patch #1 exactly the same and added a
second patch to address this case. Hopefully it works for you.

-Doug