From nobody Wed Feb 11 05:41:43 2026 Received: from out-176.mta1.migadu.com (out-176.mta1.migadu.com [95.215.58.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5D985331A50; Thu, 13 Nov 2025 08:52:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.176 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763023930; cv=none; b=p0ty8olES6/NxH28mV7qAH2o6wO+G7o9oHmvn1rpgFprPkUpOqgRjgXwhIOqb9J3aEd7SZGffp053LU8efkDF2YLLDsODfl6uXospukdz98NMGKs7SuNDCAccZjfbsV20bZYOv7UOUIx8AzJDNLTZeprYEB8+Ao33eDPFCJXtKU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763023930; c=relaxed/simple; bh=JPAS0d6/FsHNsKwO/Kj6xI4QGh3/pxx/xGZu1WXst4I=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=oTJ1VPmyQubOgJFgSOn7wVj4UrzEovxX7WHvi3Re6/w9DdYOlbfLdw6TNDHO0UjN9QxOcx/X2nexdfmI8PVd/CGBQj0kArUmVP8cqNaWuc0yWffQMUzCjoKAUuGG3zvIJz5i0Ao0JcdrTgM6Eol0QZFq0eubGpiDqUnWhsDEWwY= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=gHPS91dK; arc=none smtp.client-ip=95.215.58.176 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="gHPS91dK" Date: Thu, 13 Nov 2025 10:51:46 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1763023915; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=rEay/9/r1tEkOn0OY8xvKCykX8l3CCoErIpDTy4ypTY=; b=gHPS91dK5vXQeENx4ujySUa6w3Xni8Sk252usYwo/0/JyDZQCySeDZJVsfwEA1wojPVyB1 viVJtnhxt9Wfs19XyBGs6eTsZc4hRWcxxJx4Y3AtsavBkmW+QF44Cf5eQcgXJEfrVYiRMm 6y3MdEziZNzrio3Bfo45ca1Pi+19g80= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Matti Vaittinen To: Matti Vaittinen , Matti Vaittinen Cc: Lee Jones , Pavel Machek , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Sebastian Reichel , Liam Girdwood , Mark Brown , Michael Turquette , Stephen Boyd , Matti Vaittinen , Linus Walleij , Bartosz Golaszewski , Alexandre Belloni , linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, linux-rtc@vger.kernel.org, Andreas Kemnade Subject: [PATCH v4 02/16] dt-bindings: battery: Clarify trickle-charge Message-ID: Reply-To: Matti Vaittinen References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="/AY4lj8L7jzQOl84" Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT --/AY4lj8L7jzQOl84 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" From: Matti Vaittinen The term 'trickle-charging' is used to describe a very slow charging phase, where electrons "trickle-in" the battery. There are two different use-cases for this type of charging. At least some Li-Ion batteries can benefit from very slow, constant current, pre-pre phase 'trickle-charging', if a battery is very empty. Some other batteries use top-off phase 'trickle-charging', which is different from the above case. The battery bindings use the term 'trickle-charge' without specifying which of the use-cases properties are addressing. This has already caused some confusion. Clarify that the 'trickle-charge-current-microamp' refers to the first one, the "pre-pre" -charging use-case. Suggested-by: Krzysztof Kozlowski Signed-off-by: Matti Vaittinen Reviewed-by: Krzysztof Kozlowski Reviewed-by: Linus Walleij --- Revision history: v3 =3D> : - No changes v2 =3D> v3: - New patch --- .../devicetree/bindings/power/supply/battery.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/power/supply/battery.yaml b/= Documentation/devicetree/bindings/power/supply/battery.yaml index 491488e7b970..bfb7b716ae13 100644 --- a/Documentation/devicetree/bindings/power/supply/battery.yaml +++ b/Documentation/devicetree/bindings/power/supply/battery.yaml @@ -64,7 +64,12 @@ properties: description: battery design capacity =20 trickle-charge-current-microamp: - description: current for trickle-charge phase + description: current for trickle-charge phase. + Please note that the trickle-charging here, refers "wake-up" or + "pre-pre" -charging, for very empty batteries. Similar term is also + used for "maintenance" or "top-off" -charging of batteries (like + NiMh bq24400) - that is different and not controlled by this + property. =20 precharge-current-microamp: description: current for pre-charge phase --=20 2.51.1 --/AY4lj8L7jzQOl84 Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEIx+f8wZb28fLKEhTeFA3/03aocUFAmkVnCIACgkQeFA3/03a ocV8YQf/b/PeJt3xAb7GeCMOgGXQYBNlv6AeZZQbK+OK1t54WGRkzhIctyUDozLk qsyjumHEonq2/8m7iK3Udc+5nrTyOdQXOOtfC8HICAuL33mv4a8/+0NXlAHdhK8x On283aoQJSQhsf9Pfe8xUynY/U68qMQI0ffUJRgdljXNVK+1UD2upSUbczW3SK0B bzL3D6M+OG9UtO0mUNMU9beQczLxHn3nUfghuaFNXCq9ck79yA/CvsK7ay6ySr+y 4B7fqd2h9XglYuv3fhiJ4inV4FCXM6zqgYipqROvOg5RYfi0x8sIRyfmPewwdU+E QRAjUiRmIv3jK36hdt7GF/En8ODYzw== =46NF -----END PGP SIGNATURE----- --/AY4lj8L7jzQOl84--