[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061101193014.GA29929@kroah.com>
Date: Wed, 1 Nov 2006 11:30:14 -0800
From: Greg KH <greg@...ah.com>
To: Richard Hughes <hughsient@...il.com>
Cc: Shem Multinymous <multinymous@...il.com>,
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,
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 Wed, Nov 01, 2006 at 01:26:17PM +0000, Richard Hughes wrote:
> 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>".
No, the sysfs file should just not be present.
thanks,
greg k-h
-
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