[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41840b750610251639t637cd590w1605d5fc8e10cd4d@mail.gmail.com>
Date: Thu, 26 Oct 2006 01:39:00 +0200
From: "Shem Multinymous" <multinymous@...il.com>
To: "David Woodhouse" <dwmw2@...radead.org>
Cc: "Richard Hughes" <hughsient@...il.com>,
"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,
"David Zeuthen" <davidz@...hat.com>,
"linux-thinkpad mailing list" <linux-thinkpad@...ux-thinkpad.org>
Subject: Re: [PATCH v2] Re: Battery class driver.
Hi,
On 10/26/06, David Woodhouse <dwmw2@...radead.org> wrote:
> Ok, thanks for the feedback -- I think I've done all that. It wasn't in
> 'diff -u' form so I may have misapplied it. Please confirm.
Looks perfect. And I agree that current_{,now} etc. is better than my
suggestion of current_{avg,now}.
(I used free text instead of diff -u so I can give the rationale;
should have included both, I guess).
> > I take it you don't want to deal with battery control actions for now.
>
> They're simple enough to add. We can do it when the tp driver gets
> converted over.
Sure. But It will require some thought. For example, the interface
will need to encompass the non-symmetric pair of force commands on
ThinkPads:
"discharge the battery until further notice" vs.
"don't charge the battery for N minutes".
Also, ThinkPads express the start/stop charging thresholds in
percent, whereas I imagine some other hardware will represent it as
capacity.
What other examples do we have of machines with battery control commands?
Shem
-
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