[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1162387577.5001.7.camel@hughsie-laptop>
Date: Wed, 01 Nov 2006 13:26:17 +0000
From: Richard Hughes <hughsient@...il.com>
To: Shem Multinymous <multinymous@...il.com>
Cc: Xavier Bestel <xavier.bestel@...e.fr>,
Jean Delvare <khali@...ux-fr.org>, davidz@...hat.com,
David Woodhouse <dwmw2@...radead.org>,
Dan Williams <dcbw@...hat.com>, linux-kernel@...r.kernel.org,
devel@...top.org, sfr@...b.auug.org.au, len.brown@...el.com,
greg@...ah.com, benh@...nel.crashing.org,
linux-thinkpad mailing list <linux-thinkpad@...ux-thinkpad.org>,
Pavel Machek <pavel@...e.cz>
Subject: Re: [PATCH v2] Re: Battery class driver.
On Tue, 2006-10-31 at 16:06 +0200, Shem Multinymous wrote:
>
> In the case at hand we have mWh and mAh, which measure different
> physical quantities. You can't convert between them unless you have
> intimate knowledge of the battery's chemistry and condition, which we
> don't.
I'm thinking specifically for ACPI at the moment.
When ACPI can't work out a value, i.e. it's not known, it returns a
value of 0xFFFFFFFF. This can happen either for a split second on
disconnect, or if the hardware really doesn't know the value.
With the battery class driver, how would that be conveyed? Would the
sysfs file be deleted in this case, or would the value of the sysfs key
be something like "<invalid>".
This is something I'm just thinking about for the HAL backend, and
whatever is decided should probably be documented.
Richard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists