linux-kernel - Re: [PATCH v3 0/2] power: supply: gpio-charger: add support for default charge current limit

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] [day] [month] [year] [list]

Message-Id: <173479644258.3359498.1738381706387831556.b4-ty@collabora.com>
Date: Sat, 21 Dec 2024 16:54:02 +0100
From: Sebastian Reichel <sebastian.reichel@...labora.com>
To: Sebastian Reichel <sre@...nel.org>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, 
 Dimitri Fedrau <dimitri.fedrau@...bherr.com>
Cc: linux-pm@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Dimitri Fedrau <dima.fedrau@...il.com>, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v3 0/2] power: supply: gpio-charger: add support for
 default charge current limit


On Wed, 18 Dec 2024 09:34:59 +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. At the moment the driver defaults to smallest charge
> current limitation for safety reasons. When disabling charging is
> supported, which should be common, the driver defaults to non charging on
> probe. By having a default, charging can be enabled on probe for such
> devices.
> 
> [...]

Applied, thanks!

[1/2] dt-bindings: power: supply: gpio-charger: add support for default charge current limit
      commit: 0a219d6fd7ab89177a6fa49539def43694154d50
[2/2] power: supply: gpio-charger: add support for default charge current limit
      commit: de68987480cb92702eab14cf62ec2aa1bae5c867

Best regards,
-- 
Sebastian Reichel <sebastian.reichel@...labora.com>