public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Yves-Alexis Perez <corsac@debian.org>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: linux-acpi@vger.kernel.org, Evgeni Golov <evgeni@debian.org>
Subject: Re: Battery information in sysfs for userspace tools
Date: Mon, 18 May 2009 12:57:54 +0200	[thread overview]
Message-ID: <1242644274.8339.18.camel@miria> (raw)
In-Reply-To: <4A0F2AEC.9060802@gmail.com>

On dim, 2009-05-17 at 01:06 +0400, Alexey Starikovskiy wrote:
> Currently, sysfs interface repeats brokenness of /proc/acpi/battery 
> interface.

Hmmh, ok, but it seems to have change recently (since powertop and
acpitools are definitely wrong when it comes to that)

[…]
> The proper way to handle it is to check for 'energy_now' and if it is 
> present, look for 'power_now'. It should be
> present in 2.6.30 and later kernels (remaining time 
> energy_now/power_now). If it is not present (as in 2.6.29), then you 
> should assume that 'current_now' has value in uW, and remaining time
> is energy_now/current_now.
> If you have 'charge_now', remaining time is charge_now/current_now 
> without any complications.

Wow. Thanks for the info, that's definitely not really easily
guessable :) It'd be nice to have that documented somewhere until things
settle down a bit and the situation becomes unbroken.

Cheers,
-- 
Yves-Alexis

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-05-18 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15  8:07 Battery information in sysfs for userspace tools Yves-Alexis Perez
2009-05-16 21:06 ` Alexey Starikovskiy
2009-05-18 10:57   ` Yves-Alexis Perez [this message]

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=1242644274.8339.18.camel@miria \
    --to=corsac@debian.org \
    --cc=aystarik@gmail.com \
    --cc=evgeni@debian.org \
    --cc=linux-acpi@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