From: Merlijn Wajer <merlijn@wizzup.org>
To: Pavel Machek <pavel@ucw.cz>, Tony Lindgren <tony@atomide.com>
Cc: Sebastian Reichel <sre@kernel.org>,
linux-pm@vger.kernel.org, linux-omap@vger.kernel.org,
"Arthur D." <spinal.by@gmail.com>
Subject: Re: [PATCH 1/3] RFC: power: supply: cpcap-battery: Add helper for rough capacity
Date: Tue, 21 Jan 2020 11:42:39 +0100 [thread overview]
Message-ID: <db73a651-afc4-5c3d-0610-ccb13b8cc0d3@wizzup.org> (raw)
In-Reply-To: <20200121095712.GC6934@amd>
[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]
On 21/01/2020 10:57, Pavel Machek wrote:
> Hi!
>
>> Get a rough battery charge estimate until we've seen a high or low
>> battery level. After that we can use the coulomb counter to calculate
>> the battery capacity.
>>
>> Note that I should probably update this to support ocv-capacity-table
>> before this makes sense to apply. With ocv-capacity-table we should be
>> able to estimate battery state as described in the documentation for
>> Documentation/devicetree/bindings/power/supply/battery.txt.
>
> Maybe we should let userspace do that?
>
> https://github.com/pavelmachek/libbattery
Unless this gets integrated in UPower, My point of view is that
userspace probably wants some uniform approach. Kernel interface
definitely is one uniform interface that would also get picked up by UPower.
Cheers,
Merlijn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-01-21 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 20:11 [PATCH 1/3] RFC: power: supply: cpcap-battery: Add helper for rough capacity Tony Lindgren
2020-01-19 20:11 ` [PATCH 2/3] RFC: power: supply: cpcap-battery: Save high and low states Tony Lindgren
2020-01-19 20:11 ` [PATCH 3/3] RFC: power: supply: cpcap-battery: Implement capacity percentage Tony Lindgren
2020-01-21 9:57 ` [PATCH 1/3] RFC: power: supply: cpcap-battery: Add helper for rough capacity Pavel Machek
2020-01-21 10:42 ` Merlijn Wajer [this message]
2020-01-21 22:25 ` Pavel Machek
2020-01-23 16:02 ` Tony Lindgren
2020-03-10 4:54 ` Arthur D.
2020-03-10 15:39 ` Tony Lindgren
2020-03-10 18:35 ` Arthur D.
2020-03-11 14:23 ` Tony Lindgren
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=db73a651-afc4-5c3d-0610-ccb13b8cc0d3@wizzup.org \
--to=merlijn@wizzup.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=spinal.by@gmail.com \
--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).