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: <20241216181239.GA462174@debian>
Date: Mon, 16 Dec 2024 19:12:39 +0100
From: Dimitri Fedrau <dima.fedrau@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Dimitri Fedrau <dimitri.fedrau@...bherr.com>,
	Sebastian Reichel <sre@...nel.org>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, linux-pm@...r.kernel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: power: supply: gpio-charger: add
 support for default charge current limit

Am Mon, Dec 16, 2024 at 11:04:40AM +0100 schrieb Krzysztof Kozlowski:
> On Fri, Dec 13, 2024 at 08:32:33PM +0100, Dimitri Fedrau wrote:
> > With DT properties charge-current-limit-gpios and
> > charge-current-limit-mapping one can define charge current limits in uA
> > using up to 32 GPIOs. Add property charge-current-limit-default-microamp
> > which selects a default charge current limit that must be listed in
> > charge-current-limit-mapping.
> 
> Last time you wrote the point of it is to avoid defaulting to 0 A for
> charging, because existing implementation uses smallest possible value.
> This is supposed to be here in commit msg.
>
Will add it. Thanks for reviewing.

Best regards,
Dimitri

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ