From: Liam Breck <liam@networkimprov.net>
To: Sebastian Reichel <sre@kernel.org>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
Tony Lindgren <tony@atomide.com>,
Matt Ranostay <matt@ranostay.consulting>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4 2/8] devicetree: power: add battery state machine documentation
Date: Sun, 29 Jan 2017 18:46:10 -0800 [thread overview]
Message-ID: <CAKvHMgQFj1K2yLH3bRWYJDqB9qSVU_Gi_n2ZQB_scyg-TRCroA@mail.gmail.com> (raw)
In-Reply-To: <20170130023934.l5s7jwaozcjovqhc@earth>
On Sun, Jan 29, 2017 at 6:39 PM, Sebastian Reichel <sre@kernel.org> wrote:
> Hi,
>
> On Sun, Jan 29, 2017 at 03:32:10PM -0800, Liam Breck wrote:
>> On Sun, Jan 29, 2017 at 10:06 AM, Sebastian Reichel <sre@kernel.org> wrote:
>> > On Sun, Jan 22, 2017 at 02:22:12PM -0800, Liam Breck wrote:
>> ...
>> >> +Batteries must be referenced by chargers and/or fuel-gauges
>> >> +using a phandle. The phandle's property should be named
>> >> +"monitored-battery".
>> >> +
>> >> +Example:
>> >> +
>> >> + bat: battery {
>> >> + compatible = "fixed-battery";
>> >> + terminate-microvolt = <3700000>;
>> >> + design-microwatt-hours = <5290000>;
>> >> + design-microamp-hours = <1430000>;
>> >> + };
>> >> +
>> >> + charger: charger@0 {
>> >> + ....
>> >> + monitored-battery = <&bat>;
>> >> + ...
>> >> + };
>> >> +
>> >> + fuel_gauge: fuel_gauge@0 {
>> >> + ....
>> >> + monitored-battery = <&bat>;
>> >> + ...
>> >> + };
>> >
>> > The charger stuff does does not integrate well with
>> > pre-existing support for power-supplies property
>> > described in
>> > Documentation/devicetree/bindings/power/supply/power_supply.txt
>> >
>> > I think the proper chain would be:
>> >
>> > bat: battery {
>> > compatible = "fixed-battery";
>> > terminate-microvolt = <3700000>;
>> > design-microwatt-hours = <5290000>;
>> > design-microamp-hours = <1430000>;
>> > };
>> >
>> > fuel_gauge: fuel_gauge@0 {
>> > ...
>> > monitored-battery = <&bat>;
>> > power-supplies = <&charger>;
>> > ...
>> > };
>> >
>> > charger: charger@0 {
>> > ...
>> > };
>> >
>> > I added the power-supplies node to the fuel-gauge instead of the battery,
>> > since fuel-gauge + fixed-battery is basically a smart battery.
>>
>> BQ24190 charger will need other params from a battery node. How does
>> it get them in this scenario?
>
> It should be able to get all required properties from the bq27xxx.
> Otherwise supporting smart batteries is impossible. What properties
> do you need?
These two, at a minimum:
- precharge-microamps: maximum charge current during precharge
phase (typically 20% of battery capacity)
- termination-microamps: a charge cycle terminates when the
battery voltage is above recharge threshold, and the current is below
this setting (typically 10% of battery capacity)
Sorry, I'm not seeing how the charger will obtain these from the fuel
gauge. Could you clarify with a code snippet?
next prev parent reply other threads:[~2017-01-30 2:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 7:13 [PATCH v4 0/8] power: bq27xxx: add support for NVRAM R/W access Matt Ranostay
2017-01-22 7:13 ` [PATCH v4 1/8] devicetree: property-units: add mWh and mAh units Matt Ranostay
2017-01-23 17:50 ` Rob Herring
2017-01-22 7:13 ` [PATCH v4 2/8] devicetree: power: add battery state machine documentation Matt Ranostay
2017-01-22 22:22 ` Liam Breck
2017-01-24 19:56 ` Liam Breck
[not found] ` <CAKvHMgS9ZxE2qxDqeAVRJFzerjkJV=io58aQjtU51j=kFzbYtw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-29 17:27 ` Sebastian Reichel
2017-01-26 6:19 ` Liam Breck
2017-01-26 7:02 ` Matt Ranostay
2017-01-29 17:20 ` Sebastian Reichel
2017-01-29 23:22 ` Liam Breck
2017-01-30 2:30 ` Sebastian Reichel
2017-01-30 10:54 ` Liam Breck
[not found] ` <CAKvHMgQi1tRyUXh0504rP8VUVkFVPt_4NnYTOrBXeO4dde6KMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-30 21:40 ` Liam Breck
[not found] ` <20170122222212.27086-1-liam-RYWXG+zxWwBdeoIcmNTgJF6hYfS7NtTn@public.gmane.org>
2017-01-29 18:06 ` Sebastian Reichel
2017-01-29 23:32 ` Liam Breck
[not found] ` <CAKvHMgTrFjjEWwK-NeGOF1o6KRQPXYUvcqWcDwaW+5ZKjQ7VZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-30 2:39 ` Sebastian Reichel
2017-01-30 2:46 ` Liam Breck [this message]
2017-01-31 20:59 ` Liam Breck
[not found] ` <20170122071404.9654-1-matt-sk+viVC6FLCDq+mSdOJa79kegs52MxvZ@public.gmane.org>
2017-01-22 7:13 ` [PATCH v4 3/8] power: power_supply: add battery information struct Matt Ranostay
[not found] ` <20170122071404.9654-4-matt-sk+viVC6FLCDq+mSdOJa79kegs52MxvZ@public.gmane.org>
2017-01-29 18:23 ` Sebastian Reichel
2017-01-22 7:14 ` [PATCH v4 4/8] power: power_supply: add battery info platform data retrieval Matt Ranostay
[not found] ` <20170122071404.9654-5-matt-sk+viVC6FLCDq+mSdOJa79kegs52MxvZ@public.gmane.org>
2017-01-29 18:28 ` Sebastian Reichel
2017-01-22 7:14 ` [PATCH v4 5/8] power: bq27xxx_battery: add BQ27425 chip id Matt Ranostay
2017-01-22 7:14 ` [PATCH v4 7/8] devicetree: power: bq27xxx: add monitored battery documentation Matt Ranostay
2017-01-22 7:14 ` [PATCH v4 6/8] power: bq27xxx_battery: add i2c bulk read/write functions Matt Ranostay
2017-01-29 18:38 ` Sebastian Reichel
2017-01-22 7:14 ` [PATCH v4 8/8] power: bq27xxx_battery: add initial state machine support Matt Ranostay
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=CAKvHMgQFj1K2yLH3bRWYJDqB9qSVU_Gi_n2ZQB_scyg-TRCroA@mail.gmail.com \
--to=liam@networkimprov.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=matt@ranostay.consulting \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).