linux-kernel - Re: Question about "regulator: core: Only count load for enabled consumers" in -next

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: <20181126125038.GA9715@sirena.org.uk>
Date:   Mon, 26 Nov 2018 12:50:38 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Brian Masney <masneyb@...tation.org>
Cc:     Doug Anderson <dianders@...omium.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Question about "regulator: core: Only count load for enabled
 consumers" in -next

On Sun, Nov 25, 2018 at 06:24:50PM -0500, Brian Masney wrote:
> On Sun, Nov 25, 2018 at 09:20:02AM -0800, Doug Anderson wrote:

> > I guess this is a workaround for drivers that don't set the load
> > properly themselves?

> I'm honestly not sure when the load should be set in the driver or in
> device tree. None of the drivers in drivers/mmc/ call
> regulator_set_load. The dt bindings describes the regulator-system-load
> property in Documentation/devicetree/bindings/regulator/regulator.txt.

Very few vendors disclose power numbers, ideally the drivers would be
providing power information especially if the load caused by the device
varies substantially at runtime (as is normal if things can go idle).

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