linux-kernel - Re: [RFC PATCH v1 0/2] Introduce dummy regulator consumer

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8a688e9f-012e-461c-a916-f06b34fdd913@sirena.org.uk>
Date: Sun, 8 Jun 2025 23:33:13 +0100
From: Mark Brown <broonie@...nel.org>
To: Aleksandrs Vinarskis <alex.vinarskis@...il.com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
	Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	jens.glathe@...schoolsolutions.biz, konrad.dybcio@....qualcomm.com
Subject: Re: [RFC PATCH v1 0/2] Introduce dummy regulator consumer

On Sat, Jun 07, 2025 at 11:25:37PM +0200, Aleksandrs Vinarskis wrote:

> There are two main reasons for this driver:
> 1. Create a pseudo-consumer in place of real devices which are not or
>    cannot be described in the device-tree. Examples would be integrated
>    USB UVC camera (present on some arm64 laptops) or dedicated keyboard
>    backlight regulator (hypothetical). Instead of leaving regulator
>    without consumer and `regulator-always-on` property, one could bind
>    to dummy consumer to save some power during suspend.

Those examples both seem like physical things that exist and can have DT
bindings written for them, why not do that?

> 2. A great development tool.

That's what the userspace consumer is there for...

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