From: Paul Ionescu <i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: question about ACPI & Smart Batteries
Date: Fri, 13 Aug 2004 01:40:34 +0300 [thread overview]
Message-ID: <pan.2004.08.12.22.40.32.120142@yahoo.com> (raw)
In-Reply-To: 20040812222936.GD30862@miramar.cse.ucsc.edu
Hi Cintia,
In CM case I think that when you look into /proc/acpi/battery/BAT0/state,
you get the instantaneous value.
So the state file is not updated unless you look in it, and then you get
the values at that moment, because the APCI code will just call _BST
method to tell you the actual values.
So, I think you can trust those values as being pretty accurate.
Paul
On Thu, 12 Aug 2004 15:29:36 -0700, Cintia B. Margi wrote:
>> For a CM battery, the OS can poll the battery state by calling _BST, or
>> set a trip point (via _BTP) and the OS will get an interrupt when the
>> battery crosses that trip.
>
> I do not want to set a trip point, but I would like to monitor the
> battery discharge process... I want to characterize the battery
> discharge behavior under different tasks, so I intend to monitor the
> battery voltage and the discharge rate (which I can obtain from
> /proc/acpi/battery/BAT0/state). What I would like to know is how often
> the state file is updated and how accurate these values are. Any idea
> where I can get this info?
>
> Thanks,
>
> Cintia
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-12 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 22:10 question about ACPI & Smart Batteries Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8470726AFF5-sBd4vmA9Se6krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-12 22:29 ` Cintia B. Margi
[not found] ` <20040812222936.GD30862-v28VZnYc+MmC5P5rv/TENfZ8FUJU4vz8@public.gmane.org>
2004-08-12 22:36 ` Tomasz Ciolek
2004-08-12 22:40 ` Paul Ionescu [this message]
[not found] ` <pan.2004.08.12.22.40.32.120142-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
2004-08-13 7:40 ` Karol Kozimor
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 22:02 Cintia B. Margi
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=pan.2004.08.12.22.40.32.120142@yahoo.com \
--to=i_p_a_u_l-/e1597as9lqavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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