From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: dimitri.fedrau@liebherr.com
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dimitri Fedrau <dima.fedrau@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: power: supply: gpio-charger: add support for fast-charge timer
Date: Fri, 30 Jan 2026 23:13:25 +0100 [thread overview]
Message-ID: <aX0peTW5KfZDXHRC@venus> (raw)
In-Reply-To: <20260109-gpio-charger-timer-v2-1-63fd1ba75830@liebherr.com>
[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]
Hi,
On Fri, Jan 09, 2026 at 07:41:19PM +0100, Dimitri Fedrau via B4 Relay wrote:
> From: Dimitri Fedrau <dimitri.fedrau@liebherr.com>
>
> On some devices like TIs BQ24081 battery charger it is possible to activate
> or deactivate a fast-charge timer that provides a backup safety for charge
> termination via GPIO. In case of the BQ24081 it is a fixed 7-hour timer.
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Dimitri Fedrau <dimitri.fedrau@liebherr.com>
> ---
With the time being charger specific, this is not a good solution
for the generic gpio-charger compatible. You should add a compatible
for the BQ24081 (using gpio-charger as fallback) and then only allow
'fast-charge-timer-gpios' for the BQ24081.
Greetings,
-- Sebastian
> Documentation/devicetree/bindings/power/supply/gpio-charger.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/power/supply/gpio-charger.yaml b/Documentation/devicetree/bindings/power/supply/gpio-charger.yaml
> index 25826bfc289c1c00c338fd0cee2ae6932529cfc3..0edacc104186497118d4ba41f80947009a9aacf6 100644
> --- a/Documentation/devicetree/bindings/power/supply/gpio-charger.yaml
> +++ b/Documentation/devicetree/bindings/power/supply/gpio-charger.yaml
> @@ -62,6 +62,10 @@ properties:
> description: Default charge current limit. Must be listed in
> charge-current-limit-mapping.
>
> + fast-charge-timer-gpios:
> + maxItems: 1
> + description: GPIO used for enabling/disabling the fast-charge timer
> +
> required:
> - compatible
>
> @@ -97,4 +101,5 @@ examples:
> <700000 0x01>, // 700 mA => GPIO A.12 high
> <0 0x02>; // 0 mA => GPIO A.11 high
> charge-current-limit-default-microamp = <700000>;
> + fast-charge-timer-gpios = <&gpioA 13 GPIO_ACTIVE_LOW>;
> };
>
> --
> 2.39.5
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-30 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 18:41 [PATCH v2 0/2] power: supply: gpio-charger: add support for fast-charge timer Dimitri Fedrau via B4 Relay
2026-01-09 18:41 ` [PATCH v2 1/2] dt-bindings: " Dimitri Fedrau via B4 Relay
2026-01-30 22:13 ` Sebastian Reichel [this message]
2026-01-09 18:41 ` [PATCH v2 2/2] " Dimitri Fedrau via B4 Relay
2026-01-30 22:19 ` Sebastian Reichel
2026-02-04 12:44 ` Dimitri Fedrau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aX0peTW5KfZDXHRC@venus \
--to=sebastian.reichel@collabora.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=dimitri.fedrau@liebherr.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox