From: Pavel Machek <pavel@ucw.cz>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
cbou@mail.ru, dwmw2@infradead.org,
LKML <linux-kernel@vger.kernel.org>,
linux-embedded@vger.kernel.org
Subject: Re: [POWER] battery calibration parameters from sysfs
Date: Sun, 13 Dec 2009 14:19:22 +0100 [thread overview]
Message-ID: <20091213131921.GA1437@ucw.cz> (raw)
In-Reply-To: <A6D19A13FE030A409EC4362C172E091F0E0A1FA1@eseldmw101.eemea.ericsson.se>
> One of the things we're facing is Android, which has
> its userspace in plain Java JNI at the end of this link:
> http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=s
> ervices/jni/com_android_server_BatteryService.cpp;h=8e7cadc6b680fc420d34
> 1faa094c71922946fdab;hb=HEAD
>
> If you browse down to line 275 you can see it parse the sysfs
> attribute "capacity", then this propagates up to the battery
> status indicator on *all* Android phones out there. So if
> you want to run Android unmodified, this is what you need to
> provide. They are effectively using the power sysfs as
> their hardware abstraction layer in this case.
>
> Note: I'm not claiming that Android is doing it right or that
> we can't modify this code or so, it's just that this is the way
> a few million Android devices out there are actually doing it.
Users can't modify them, so they don't count...
...but then there are all the systems that rely on /proc/apm
emulation, like openembedded popular on sharp zaurus...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-12-13 13:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 10:42 Linus Walleij
2009-12-04 10:49 ` Mark Brown
2009-12-04 14:17 ` Mark Brown
2009-12-05 13:08 ` Linus Walleij
2009-12-05 17:45 ` Mark Brown
2009-12-07 11:48 ` Mark Brown
2009-12-07 14:07 ` Linus Walleij
2009-12-07 16:56 ` Mark Brown
2009-12-08 5:27 ` Brian Swetland
2009-12-08 10:28 ` Mark Brown
2009-12-13 13:24 ` Pavel Machek
2009-12-14 12:12 ` Mark Brown
2009-12-14 21:22 ` Pavel Machek
2009-12-14 23:43 ` Aras Vaichas
2009-12-15 3:02 ` Bill Gatliff
2009-12-15 22:58 ` Aras Vaichas
2009-12-15 23:32 ` Stanislav Brabec
2009-12-16 9:40 ` Andy Green
2009-12-18 8:48 ` Pavel Machek
2009-12-16 22:53 ` Pavel Machek
2009-12-13 13:19 ` Pavel Machek [this message]
2009-12-14 11:50 ` Mark Brown
2009-12-14 11:58 ` Pavel Machek
2009-12-14 12:14 ` Mark Brown
2009-12-04 11:34 ` Alexander Clouter
2009-12-06 20:52 ` Greg KH
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=20091213131921.GA1437@ucw.cz \
--to=pavel@ucw.cz \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cbou@mail.ru \
--cc=dwmw2@infradead.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®