From: Michael Heinemann <posted@heine.so>
To: linux-pm@vger.kernel.org
Subject: sbs-battery: Reading CHARGE in uAh
Date: Thu, 06 Jul 2017 17:23:02 +0200 [thread overview]
Message-ID: <d760d0a1b38fbda966caaefc63677a56@heine.so> (raw)
Hi,
I got an INSPIRED ENERGY NH2057 Battery which is compliant to SBS
Specification Version 1.1.
The Battery is generally working but I noticed that the values I get
from sysfs for the CHARGE values
are identical to the values I get as ENERGY and they are in uWh.
According to the power_supply_class
documentation CHARGE should be in uAh and ENERGY in uWh.
So I took a look into the drivers/power/supply/sbs-battery.c and noticed
a possible bug in the code
when switching from BATTERY_MODE_WATTS to BATTERY_MODE_AMPS:
The configuration bit, according to the SBS Spec, is bit 15 of the
BatteryMode Register.
These two modes are reflected in the code as:
enum sbs_battery_mode {
BATTERY_MODE_AMPS,
BATTERY_MODE_WATTS
};
When I look into the 'sbs_set_battery_mode' function I don't see any
point where these mode bits are
shifted to bit 15. When I debug I only see the register being changed
from 0x8000 to 0x8001 and back.
So I'm a bit confused, is this actually working for somebody? I see in
the 'for-next' branch [1] that
there is currently work done to add a mutex to the mode switch. So at
least it seems to be working for
some people. But I don't see why. Am I missing something?
Regards,
Michael
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git/log/drivers/power/supply/sbs-battery.c?h=for-next
next reply other threads:[~2017-07-06 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 15:23 Michael Heinemann [this message]
2017-07-07 1:49 ` sbs-battery: Reading CHARGE in uAh Phil Reid
2017-07-07 8:01 ` Michael Heinemann
2017-07-07 8:27 ` Phil Reid
2017-07-07 13:06 ` Michael Heinemann
2017-07-10 1:35 ` Phil Reid
2017-07-10 7:54 ` Michael Heinemann
2017-07-10 8:04 ` Phil Reid
2017-07-10 15:42 ` Michael Heinemann
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=d760d0a1b38fbda966caaefc63677a56@heine.so \
--to=posted@heine.so \
--cc=linux-pm@vger.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