From: Rob Herring <robh@kernel.org>
To: Quentin Schulz <quentin.schulz@free-electrons.com>
Cc: sre@kernel.org, mark.rutland@arm.com, wens@csie.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, liam@networkimprov.net,
thomas.petazzoni@free-electrons.com,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH 2/4] dt-bindings: power: battery: add constant-charge-current-max-microamp property
Date: Mon, 15 May 2017 15:14:20 -0500 [thread overview]
Message-ID: <20170515201420.o5lf55gbfd4pgawb@rob-hp-laptop> (raw)
In-Reply-To: <20170511134221.5569-3-quentin.schulz@free-electrons.com>
On Thu, May 11, 2017 at 03:42:18PM +0200, Quentin Schulz wrote:
> This adds the constant-charge-current-max-microamp property to the list
> of optional properties of the battery.
>
> The constant charge current is critical for batteries as they can't
> handle all charge currents.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
> ---
> Documentation/devicetree/bindings/power/supply/battery.txt | 2 ++
> 1 file changed, 2 insertions(+)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-05-15 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 13:42 [PATCH 0/4] set battery info on AXP20X and AXP22X from DT Quentin Schulz
2017-05-11 13:42 ` [PATCH 1/4] power: supply: axp20x_battery: add support for DT battery Quentin Schulz
2017-05-16 5:18 ` Chen-Yu Tsai
2017-05-16 6:33 ` Quentin Schulz
2017-06-08 15:58 ` Sebastian Reichel
2017-05-11 13:42 ` [PATCH 2/4] dt-bindings: power: battery: add constant-charge-current-max-microamp property Quentin Schulz
2017-05-15 20:14 ` Rob Herring [this message]
2017-05-11 13:42 ` [PATCH 3/4] power: supply: power_supply_core: add constant-charge-current optional property Quentin Schulz
2017-05-11 13:42 ` [PATCH 4/4] power: supply: axp20x_battery: add DT support for battery max constant charge current Quentin Schulz
2017-06-08 15:58 ` Sebastian Reichel
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=20170515201420.o5lf55gbfd4pgawb@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=liam@networkimprov.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=quentin.schulz@free-electrons.com \
--cc=sre@kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wens@csie.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
all inboxes | Powered by JetHome®