linux-kernel - Re: [PATCH v2] regulator: gpio: Correct default GPIO state to LOW

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: <4e641ee2-1170-436e-967b-a1809d0f3b06@sirena.org.uk>
Date: Wed, 29 May 2024 14:37:00 +0100
From: Mark Brown <broonie@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Liam Girdwood <lgirdwood@...il.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Rob Herring <robh+dt@...nel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] regulator: gpio: Correct default GPIO state to LOW

On Wed, May 29, 2024 at 03:19:04PM +0200, Geert Uytterhoeven wrote:
> On Wed, May 29, 2024 at 3:15 PM Mark Brown <broonie@...nel.org> wrote:

> > The risk here is that we start glitching the power where previously we
> > didn't.  This does make me nervous.

> /me too

> The alternative is to change the GPIO regulator DT bindings document
> to match the code...

Yup, that makes me feel a lot safer than changing the code.

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