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: <20251020151511.1fd8611b@kemnade.info>
Date: Mon, 20 Oct 2025 15:15:11 +0200
From: Andreas Kemnade <andreas@...nade.info>
To: Lee Jones <lee@...nel.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Alistair Francis
 <alistair@...stair23.me>, Liam Girdwood <lgirdwood@...il.com>, Mark Brown
 <broonie@...nel.org>, Shawn Guo <shawnguo@...nel.org>, Sascha Hauer
 <s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>,
 Fabio Estevam <festevam@...il.com>, Frank Li <Frank.li@....com>, Andreas
 Kemnade <akemnade@...nel.org>, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, imx@...ts.linux.dev,
 linux-arm-kernel@...ts.infradead.org, Krzysztof Kozlowski
 <krzysztof.kozlowski@...aro.org>
Subject: Re: (subset) [PATCH v3 1/3] dt-bindings: mfd: sy7636a: Add missing
 gpio pins and supply

On Wed, 08 Oct 2025 16:31:57 +0100
Lee Jones <lee@...nel.org> wrote:

> On Wed, 17 Sep 2025 09:14:29 +0200, Andreas Kemnade wrote:
> > To be able to fully describe how the SY7636A is connected to the system,
> > add properties for the EN and VCOM_EN pins. To squeeze out every bit
> > of unused current, in many devices it is possible to power off the
> > complete chip. Add an input regulator to allow that.
> > 
> >   
> 
> Applied, thanks!
> 
> [1/3] dt-bindings: mfd: sy7636a: Add missing gpio pins and supply
>       commit: 7d983e997cb53d4c48b61b105163c31c92a35823
> 
hmm, what is the fate of this? I remember having seen this in your
for-mfd-next-next branch. But now I cannot find it neither in
your mfd-next nor your mfd-next-next nor general linux-next.

Regards,
Andreas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ