linux-kernel - Re: [PATCH v2 0/4] gpio: deprecate and track the removal of GPIO workarounds for regulators

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: <df350510-64c9-46b4-9f82-ebd6b04bba36@sirena.org.uk>
Date: Mon, 7 Apr 2025 14:33:49 +0100
From: Mark Brown <broonie@...nel.org>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Linus Walleij <linus.walleij@...aro.org>, linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH v2 0/4] gpio: deprecate and track the removal of GPIO
 workarounds for regulators

On Mon, Apr 07, 2025 at 03:29:09PM +0200, Bartosz Golaszewski wrote:

> Basically: we may set the GPIO to 1 but it was already enabled and we
> tell consumers the regulator was just enabled when it wasn't OR we set
> the GPIO to 0 and tell consumers the regulator was disabled when there
> are still users of this GPIO so it's not true either.

> AFAICT, it's used in a few places to put the regulator consumer in
> reset if the power was *actually* disabled.

Yes, and also do things like not bother to reinitialise the hardware if
we kept the power on.

> I'll think about how that could be improved.

Thanks.

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