linux-kernel - Re: PoE complex usage of regulator API

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: <ZjBWE5XEJjHjftsn@finisterre.sirena.org.uk>
Date: Tue, 30 Apr 2024 11:23:15 +0900
From: Mark Brown <broonie@...nel.org>
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: Oleksij Rempel <o.rempel@...gutronix.de>,
	Kyle Swenson <kyle.swenson@....tech>,
	Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: PoE complex usage of regulator API

On Mon, Apr 29, 2024 at 07:28:48PM +0200, Kory Maincent wrote:
> Mark Brown <broonie@...nel.org> wrote:
> > On Fri, Apr 26, 2024 at 12:42:53PM +0200, Kory Maincent wrote:

> That's right I was focusing on power where I could use already implemented
> voltage and current callbacks. Would you be interested to a new get_current()
> callback to know the current and allows regulator to deduce the consumed power
> or should it be specific to PSE subsystem.

That feels like it belongs in hwmon or possibly power rather than in the
regulator API but it does feel like it's generally useful rather than
PSE specific.

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