From: Dimitri Fedrau <dima.fedrau@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Dimitri Fedrau <dimitri.fedrau@liebherr.com>,
Sebastian Reichel <sre@kernel.org>, 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
Subject: Re: [PATCH v2 1/2] dt-bindings: power: supply: gpio-charger: add support for default charge current limit
Date: Mon, 16 Dec 2024 19:12:39 +0100 [thread overview]
Message-ID: <20241216181239.GA462174@debian> (raw)
In-Reply-To: <2tk4mnzzhr3se3sts7gyt27izhlsmzajvdgfszubgy74wggeom@kggdt4go667b>
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
next prev parent reply other threads:[~2024-12-16 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 19:32 [PATCH v2 0/2] power: supply: gpio-charger: add support for default charge current limit Dimitri Fedrau via B4 Relay
2024-12-13 19:32 ` [PATCH v2 1/2] dt-bindings: " Dimitri Fedrau via B4 Relay
2024-12-16 10:04 ` Krzysztof Kozlowski
2024-12-16 18:12 ` Dimitri Fedrau [this message]
2024-12-13 19:32 ` [PATCH v2 2/2] " Dimitri Fedrau via B4 Relay
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=20241216181239.GA462174@debian \
--to=dima.fedrau@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dimitri.fedrau@liebherr.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@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