From: Mark Brown <broonie@kernel.org>
To: Lukasz Majewski <l.majewski@samsung.com>
Cc: "Comaschi, F." <fcomaschi@tue.nl>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Chander Kashyap <chander.kashyap@linaro.org>,
Linux PM List <linux-pm@lists.linux-foundation.org>
Subject: Re: Arndale power management
Date: Wed, 17 Jul 2013 12:33:52 +0100 [thread overview]
Message-ID: <20130717113352.GQ22506@sirena.org.uk> (raw)
In-Reply-To: <20130716092345.28c8d655@amdc308.digital.local>
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
On Tue, Jul 16, 2013 at 09:23:45AM +0200, Lukasz Majewski wrote:
> > > Maybe it is
> > > possible to communicate with the on-board PMIC?
> You can look into the PMIC spec if some detailed informations are
> exposed. Moreover each battery shall be described by a model, which
> PMIC uses e.g. for accurate charging.
> PMICs at Exynos4 are communicating via I2C and provide information
> about battery state of charge (SoC). You can monitor this value over
> time and on this basis get (very coarse) estimation of power
> consumption.
There are enormous difficulties in getting useful information from
batteries and chargers - due to things like the battery chemistry
changing over time and thermal dependencies what you get back is so
coarse grained it's of very little use for power metering. There's also
the fact that on the Arndale the charger isn't wired up accessibly.
Power monitoring is generally done with test equipment rather than on
board features - Versatile Express is very unusual here. The usual
strategy at system level is to put an ammeter or power meter in line
with the main power supply; otherwise you need the board to have test
access to allow you to hook into individual supplies (typically done
with jumpers in line with the supplies).
> I can only give you a hint there (since I didn't worked with Arndale ...
> yet) - measure current and voltage provided for SoC core Vdd plane.
I've not checked the schematics but there's nothing visible on the board
that I'd associate with current monitoring except the wall supply.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-17 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <611CFE9D6FBBDC4B97935A5287A11345014441@XSERVER21B.campus.tue.nl>
2013-07-16 6:43 ` Arndale power management Viresh Kumar
2013-07-16 7:23 ` Lukasz Majewski
2013-07-17 11:33 ` Mark Brown [this message]
2013-07-16 8:48 ` Andy Green
2013-07-25 1:58 ` Mike Turquette
[not found] ` <611CFE9D6FBBDC4B97935A5287A1134501BB6D@XSERVER21B.campus.tue.nl>
[not found] ` <CAPtuhTg3YdTGy58UT9gVmp9EZNBwxaqv69A8nv_Gackyc5qc5Q@mail.gmail.com>
2013-07-26 6:06 ` Comaschi, F.
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=20130717113352.GQ22506@sirena.org.uk \
--to=broonie@kernel.org \
--cc=chander.kashyap@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=fcomaschi@tue.nl \
--cc=l.majewski@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=viresh.kumar@linaro.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